Method and apparatus for transmitting and receiving signals in a wireless communication system

The method optimizes channel occupancy in wireless communication systems by managing uplink and downlink transmissions based on configured conditions to avoid idle periods, addressing inefficiencies and collisions in shared spectrum environments.

JP2024542406APending Publication Date: 2024-11-15LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024527146
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-12-05
Filing Date
2022-12-05
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently transmitting and receiving signals due to overlapping channel occupancy periods and idle periods, leading to inefficiencies and potential collisions.

Method used

A method for terminals and base stations to manage channel occupancy based on configured uplink and downlink transmissions using upper layer signaling, with conditions for determining whether to perform or drop transmissions to avoid overlaps with idle periods, ensuring efficient use of shared spectrum.

Benefits of technology

This approach allows for efficient transmission and reception of wireless signals by optimizing channel usage, reducing collisions, and enhancing communication efficiency in shared spectrum environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024542406000001_ABST
    Figure 2024542406000001_ABST
Patent Text Reader

Abstract

According to at least one of various embodiments of the present invention, a UE receives configuration information for a configured UL (uplink) transmission on a shared spectrum through higher layer signaling, and performs a channel access process for the configured UL transmission. In the channel access process, the UE determines whether to perform or drop the configured UL transmission based on whether the configured UL transmission occurs after the start of a first period configured to support UE-initiated channel occupancy and whether the configured UL transmission overlaps with an idle period included in / corresponding to the first period.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to wireless communication systems, and more particularly to a method and apparatus for transmitting or receiving uplink / downlink radio signals in a wireless communication system. [Background technology]

[0002] Wireless communication systems have been widely deployed to provide various communication services such as voice and data. Generally, wireless communication systems are multiple access systems that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency division multiple access (SC-FDMA) systems. Summary of the Invention [Problem to be solved by the invention]

[0003] The technical problem to be solved is to provide a method and apparatus for efficiently transmitting and receiving radio signals.

[0004] The technical problems to be achieved are not limited to these, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the following description. [Means for solving the problem]

[0005] According to one aspect of the present invention, a method for transmitting a signal by a terminal (UE) in a wireless communication system includes receiving configuration information for a configured uplink (UL) transmission on a shared spectrum via higher layer signaling, and performing a channel access procedure for the configured uplink transmission. The channel access procedure includes checking a plurality of conditions for determining whether to perform or drop the configured uplink transmission based on whether the configured uplink transmission occurs after the start of a first interval configured to support UE-initiated channel occupancy and overlaps with an idle period included in the first interval. The plurality of conditions include: i) a first condition that the terminal has not initiated channel occupancy in the first interval; ii) a second condition that the configured uplink transmission occurs within a second interval configured to support base station (BS)-initiated channel occupancy and ends before an idle period of the second interval; and iii) a third condition that channel occupancy by the BS has already been initiated in the second interval. In order to perform the configured UL transmission, all of the above conditions must be satisfied.

[0006] The terminal may drop the configured UL transmission based on any one of the plurality of conditions not being met.

[0007] The terminal may drop the configured UL transmission based on the fact that channel occupation by the terminal has already started in the first period.

[0008] The terminal may drop the configured UL transmission based on the fact that the configured UL transmission occurs within the second interval but overlaps with an idle interval of the second interval.

[0009] The terminal may drop the configured UL transmission even if the configured UL transmission occurs within the second interval and ends before the idle interval of the second interval, without determining that channel occupation by the base station has already started in the second interval.

[0010] If the first condition, the second condition, and the third condition are all satisfied, the terminal can perform the configured UL transmission on a COT (channel occupancy time)-sharing basis in the second interval in which the base station starts channel occupation.

[0011] The terminal can drop the configured UL transmission on all of the multiple channels in the interval that overlaps with at least one of the idle intervals, regardless of whether each channel is occupied by the terminal or the base station, based on the fact that the configured UL transmission is configured on multiple channels in the frequency domain and overlaps with at least one of the idle intervals of the first interval or the idle intervals of the second interval in the time domain, and the multiple channels include a channel occupied by the terminal and a channel occupied by the base station.

[0012] The terminal may drop the configured UL transmission on all of the plurality of channels in the interval that overlaps with at least one of the idle intervals, regardless of whether each channel is occupied by the terminal or the base station, based on the fact that the configured UL transmission is configured on multiple channels in the frequency domain and overlaps with at least one of the idle intervals of the first interval or the idle interval of the second interval in the time domain, and all of the plurality of channels are not associated with the same channel occupancy.

[0013] The terminal may be configured such that the configured UL transmission is configured on multiple channels in the frequency domain and overlaps with at least one of the idle intervals of the first interval or the idle intervals of the second interval in the time domain, and the multiple conditions may include a fourth condition that all of the multiple channels are associated with the same channel occupancy.

[0014] The first interval may be periodically set via higher layer signaling for the UE-initiated channel occupancy, and the second interval may be periodically set via higher layer signaling for the BS-initiated channel occupancy.

[0015] According to another aspect of the present invention, a method for receiving a signal by a base station (BS) in a wireless communication system includes transmitting configuration information for configured uplink (UL) reception on a shared spectrum to a terminal (UE) via higher layer signaling, and performing the configured uplink reception from the terminal. Whether to perform the configured uplink reception is determined based on whether the configured uplink reception occurs after the start of a first interval configured to support UE-initiated channel occupancy and whether the configured uplink reception overlaps with an idle period included in the first interval. To perform the configured uplink reception, multiple conditions must all be satisfied, including: i) a first condition that the terminal has not initiated channel occupancy in the first interval; ii) a second condition that the configured uplink reception occurs within a second interval configured to support BS-initiated channel occupancy and ends before an idle period of the second interval; and iii) a third condition that channel occupancy by the base station has already been initiated in the second interval.

[0016] In yet another aspect of the present invention, there is provided a base station for performing the above-described method. [Effects of the Invention]

[0017] According to at least one of various embodiments, wireless signals can be efficiently transmitted and received in a wireless communication system.

[0018] The effects obtained by the present invention are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the following description. [Brief explanation of the drawings]

[0019] [Figure 1] 1 is a diagram illustrating physical channels used in a 3GPP (registered trademark) system, which is an example of a wireless communication system, and a general signal transmission method using these channels. [Figure 2] FIG. 1 is a diagram illustrating the structure of a radio frame. [Figure 3] FIG. 1 illustrates a resource grid of slots. [Figure 4] FIG. 10 is a diagram illustrating an example of mapping physical channels within a slot. [Figure 5] FIG. 1 illustrates an ACK / NACK transmission process. [Figure 6] FIG. 1 is a diagram illustrating a PUSCH (Physical Uplink Shared Channel) transmission process. [Figure 7] FIG. 10 is a diagram illustrating an example of multiplexing control information onto a PUSCH. [Figure 8] FIG. 1 illustrates a wireless communication system that supports unlicensed bands. [Figure 9] FIG. 1 illustrates a method for occupying resources in an unlicensed spectrum. [Figure 10] FIG. 1 illustrates an example of an FBE-based channel access. [Figure 11] FIG. 1 illustrates an example of an LBE-based channel accelerator. [Figure 12]10 is a flowchart illustrating a Type 1 CAP operation (eg, an example of an LBE-based channel access) of a base station for downlink signal transmission. [Figure 13] 10 is a flowchart illustrating a Type 1 CAP operation (eg, an example of LBE-based channel access) of a terminal for uplink signal transmission. [Figure 14] 1 is a diagram illustrating multiple LBT-SBs included in a frequency band (e.g., BWP) on a shared spectrum. [Figure 15] FIG. 1 illustrates an FFP according to one embodiment. [Figure 16] FIG. 1 illustrates an FFP according to one embodiment. [Figure 17] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 18] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 19] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 20] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 21] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 22] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 23] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 24] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 25] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 26] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 27] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 28] FIG. 1 is a diagram illustrating a method for transmitting and receiving signals over a shared spectrum. [Figure 29]1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 30] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 31] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 32] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 33] FIG. 1 is a diagram illustrating a DRX (Discontinuous Reception) operation applicable to the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0020] The following technologies can be used for various wireless access systems, such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A.

[0021] As more communication devices require larger communication capacities, there is an emerging need for improved mobile broadband (eMBB) communication compared to existing radio access technologies (RATs). Furthermore, massive machine-type communications (MTC), which connects multiple devices and objects to provide various services anytime and anywhere, is one of the important issues to be considered in next-generation communications. Furthermore, ultra-reliable and low latency communication (URLLC), which takes into account reliability- and latency-sensitive services / UEs, is also being discussed. Thus, the introduction of next-generation RATs taking into account enhanced mobile broadband communication (eMBB), massive MTC, and ultra-reliable and low latency communication (URLLC), etc., is being discussed, and for convenience, the present invention will refer to these technologies as new radio or new RAT (NR).

[0022] For clarity of explanation, the description will be focused on 3GPP NR, but the technical idea of ​​the present invention is not limited thereto.

[0023] In this specification, the term "setting" may be replaced with the term "configure / configuration," and the two terms may be used interchangeably. Conditional expressions (e.g., "if," "in a case," or "when") may be replaced with expressions such as "based on that" or "in a state / status." The operation or SW / HW configuration of a terminal / base station based on the satisfaction of a corresponding condition may be inferred or understood by analogy. In signal transmission and reception between wireless communication devices (e.g., base station, terminal), if the process on the receiving (or transmitting) side can be inferred or understood by analogy from the process on the transmitting (or receiving) side, the explanation may be omitted. For example, signal determination / generation / encoding / transmission on the transmitting side may be understood as signal monitoring / reception / decoding / decision on the receiving side. An expression that a terminal performs (or does not perform) a specific operation may also be interpreted as the base station operating by expecting / assuming (or expecting / assuming not) that the terminal will perform the specific operation. The expression that a base station performs (or does not perform) a specific operation can also be interpreted as the terminal operating under the expectation / assuming (or expecting / assuming not to perform) the execution of a specific operation of the base station. Furthermore, in the following description, the divisions and indexes of each section, embodiment, example, option, method, solution, etc. are for the convenience of explanation and should not be interpreted as meaning that each necessarily constitutes an independent invention or that each necessarily must be implemented individually. Furthermore, in describing each section, embodiment, example, option, method, solution, etc., unless there is explicitly conflicting / opposing technology, it is inferred / interpreted that at least some of them may be combined and implemented together, or at least some may be omitted and implemented.

[0024] In a wireless communication system, a terminal receives information from a base station via a downlink (DL), and transmits information from the base station via an uplink (UL). Information exchanged between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / purpose of the information exchanged.

[0025] FIG. 1 is a diagram illustrating physical channels used in a 3GPP NR system and a general signal transmission method using these channels.

[0026] A terminal that has been powered on in a powered-off state or that has newly entered a cell performs an initial cell search, such as establishing synchronization with a base station, in step S101. To this end, the terminal receives a synchronization signal block (SSB) from the base station. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The terminal establishes synchronization with the base station based on the PSS / SSS and obtains information such as a cell identity. The terminal also obtains broadcast information within the cell based on the PBCH. In addition, the terminal can receive a downlink reference signal (DL RS) during the initial cell search to check the status of the downlink channel.

[0027] After completing the initial cell search, the terminal receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information from the physical downlink control channel in step S102 to obtain more specific system information.

[0028] Thereafter, the terminal performs a random access procedure such as steps S103 to S106 to complete connection to the base station. To this end, the terminal transmits a preamble over a physical random access channel (PRACH) (S103) and receives a response message for the preamble over a physical downlink control channel (PRACH) and a corresponding physical downlink shared channel (S104). In the case of contention-based random access, the terminal performs a contention resolution procedure such as transmitting a further physical random access channel (S105) and receiving a physical downlink control channel (PRACH) and a corresponding physical downlink shared channel (S106).

[0029] After performing this procedure, the terminal then receives a physical downlink control channel / physical downlink shared channel (S107) and transmits a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) as a general uplink / downlink signal transmission procedure (S108). The control information transmitted by the terminal to the base station is collectively referred to as uplink control information (UCI). UCI includes a hybrid automatic repeat and reQuest acknowledgment / negative-ACK (HARQ ACK / NACK), a scheduling request (SR), channel state information (CSI), etc. CSI includes a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indication (RI), etc. UCI is generally transmitted via a PUCCH, but when control information and traffic data need to be transmitted simultaneously, it is transmitted via a PUSCH. In addition, UCI can be transmitted aperiodically via PUSCH at the request / instruction of the network.

[0030] Meanwhile, the voluntary access procedure (RACH procedure) is not limited to a procedure for initial network access (e.g., S103 to S106) and can be used for various purposes. For example, the voluntary access procedure can be used for any of, but not limited to, an RRC connection re-establishment procedure, handover, UE-triggered UL data transmission, transition from RRC_INACTIVE, SCell time alignment, system information request and beam failure recovery, and UL resource request. A UE can obtain UL synchronization and / or UL transmission resources through the voluntary access procedure. The voluntary access procedure is divided into 1) contention-based random access and 2) contention-free random access procedures.

[0031] 1) Contention-based Random Access (CBRA) is divided into 4-step CBRA and 2-step CBRA. 4-step CBRA is also called Type-1, and 2-step CBRA is also called Type-2.

[0032] First, regarding 4-step CBRA, the UE transmits Message 1 (Msg1) including a preamble associated with a specific sequence via the PRACH, and receives Message 2 (Msg2) including a Random Access Response (RAR) via the PDCCH and the corresponding PDSCH. The UE transmits Message 3 (Msg3) via the PUSCH using scheduling information in the RAR. The UE receives Message 4 (Msg4) including contention resolution information for the contention resolution process from the base station.

[0033] Next, regarding 2-step CBRA, transmission of Msg1 and Msg3 in 4-step CBRA is performed by transmitting one message A (MsgA) including PRACH and PUSCH in 2-step CBRA. MsgA includes the PRACH preamble of Msg1 and data of Msg3. Furthermore, transmission of Msg2 and Msg4 in 4-step CBRA is performed by the base station in 2-step CBRA by transmitting one message B (MsgB) including RAR and collision resolution information. MsgB includes the RAR of Msg2 and the collision resolution information of Msg4.

[0034] 2) Contention Free Random Access (CFRA) is used when a terminal is handing over to another cell or base station, or is performed when requested by a command from the base station. The basic process of CFRA is similar to that of CBRA. However, unlike CBRA, in which a terminal selects a preamble to use from multiple voluntary connection preambles, in CFRA, a dedicated voluntary connection preamble to be used by the terminal is explicitly indicated to the terminal by the base station. Information about the dedicated voluntary connection preamble is included in an RRC message (e.g., handover command) or provided to the terminal by a PDCCH order. When the voluntary connection procedure is initiated, the terminal transmits a dedicated voluntary connection preamble to the base station. When the terminal receives an voluntary connection response from the base station, the voluntary connection procedure is completed.

[0035] On the other hand, CBRA is also called CB-RACH, and CFRA is also called CF-RACH.

[0036] Figure 2 illustrates the structure of a radio frame. In NR, uplink and downlink transmissions are composed of frames. A radio frame has a length of 10 ms and is defined as two 5 ms half-frames (HF). A half-frame is defined as five 1 ms subframes (SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP). When a regular CP is used, each slot contains 14 symbols. When an extended CP is used, each slot contains 12 symbols.

[0037] Table 1 shows an example in which the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS when a general CP is used.

[0038] [Table 1]

[0039] *N slot symb :Number of symbols in slot *N frame,u slot : Number of slots in the frame * N subframe,u slot : Number of slots in a subframe

[0040] Table 2 illustrates how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS when an extended CP is used.

[0041] [Table 2]

[0042] The frame structure is merely an example, and the number of subframes, slots, and symbols in a frame can be variously changed. In an NR system, OFDM numerology (e.g., SCS) can be set to be different among multiple cells merged into one terminal. Accordingly, the (absolute time) duration of time resources (e.g., SFs, slots, or TTIs) (commonly referred to as TUs (Time Units) for convenience) consisting of the same number of symbols can be set to be different among the merged cells. Here, the symbols include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbols).

[0043] FIG. 3 illustrates a resource grid of a slot. A slot includes multiple symbols in the time domain. For example, in the case of a general CP, one slot includes 14 symbols, while in the case of an extended CP, one slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP is defined as multiple consecutive physical RBs (PRBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier includes up to N BWPs (e.g., 5 BWPs). Data communication is performed using activated BWPs, and only one BWP can be activated for one UE. Each element in the resource grid is called a resource element (RE), and one complex symbol can be mapped to it.

[0044] Figure 4 shows an example of mapping physical channels within a slot. PDCCH is transmitted in the DL control region, and PDSCH is transmitted in the DL data region. PUCCH is transmitted in the UL control region, and PUSCH is transmitted in the UL data region. GP provides a time gap when the base station and the terminal switch from transmission mode to reception mode or from reception mode to transmission mode. Some symbols at the time of switching from DL to UL within a subframe can be set as GP.

[0045] Each physical channel is described in more detail below.

[0046] The PDCCH carries Downlink Control Information (DCI). For example, the PCCCH (i.e., DCI) carries the transmission format and resource allocation of the downlink shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information for the Paging Channel (PCH), system information on the DL-SCH, resource allocation information for higher layer control messages such as voluntary access responses transmitted on the PDSCH, transmit power control commands, and activation / deactivation of Configured Scheduling (CS). The DCI includes a cyclic redundancy check (CRC), which is masked / scrambled with various identifiers (e.g., Radio Network Temporary Identifier, RNTI) depending on the owner or use of the PDCCH. For example, if the PDCCH is for a specific terminal, the CRC is masked with a terminal identifier (e.g., cell-RNTI, C-RNTI). If the PDCCH is related to paging, the CRC is masked with a Paging-RNTI (P-RNTI). If the PDCCH is related to system information (e.g., System Information Block, SIB), the CRC is masked to a System Information RNTI (SI-RNTI). If the PDCCH is related to an voluntary access response, the CRC is masked to a Random Access RNTI (RA-RNTI).

[0047] The PDCCH consists of 1, 2, 4, 8, or 16 Control Channel Elements (CCEs) depending on the Aggregation Level (AL). A CCE is a logical allocation unit used to provide a PDCCH with a predetermined code rate according to the radio channel conditions. A CCE consists of 6 Resource Element Groups (REGs). A REG is defined by one OFDM symbol and one (P)RB. The PDCCH is transmitted using a Control Resource Set (CORESET). A CORESET is defined by a set of REGs with a given pneumatic system (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE can be overlapped in the time / frequency domain. A CORESET is configured by system information (e.g., Master Information Block, MIB) or UE-specific (UE-specific) signaling through a higher layer (e.g., Radio Resource Control, RRC, layer). Specifically, the number of RBs and the number of OFDM symbols (maximum 3) that make up a CORESET are configured by higher layer signaling.

[0048] To receive / detect the PDCCH, the UE monitors PDCCH candidates. PDCCH candidates indicate the CCEs that the UE monitors for PDCCH detection. Each PDCCH candidate is defined by 1, 2, 4, 8, or 16 CCEs depending on the AL. Monitoring includes (blind) decoding of the PDCCH candidates. The set of PDCCH candidates that the UE monitors is defined as the PDCCH search space (SS). The search space includes a common search space (CSS) or a UE-specific search space (USS). The UE can obtain DCI by monitoring PDCCH candidates in one or more search spaces configured by MIB or higher layer signaling. Each CORESET is associated with one or more search spaces, and each search space is associated with one COREST. The search space is defined based on the following parameters:

[0049] -controlResourceSetId: Indicates the CORESET associated with the search space.

[0050] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring period (in slot units) and the PDCCH monitoring period offset (in slot units).

[0051] - monitoringSymbolsWithinSlot: Indicates the PDCCH monitoring symbols within the slot (for example, indicates the first symbol of SORESET).

[0052] -nrofCandidates: Indicates the number of PDCCH candidates (one of 0, 1, 2, 3, 4, 5, 6, 8) for each AL={1, 2, 4, 8, 16}.

[0053] *An opportunity (e.g., time / frequency resource) to monitor a PDCCH candidate is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities are configured within a slot.

[0054] Table 3 illustrates the characteristics of each search space type.

[0055] [Table 3]

[0056] Table 4 illustrates an example of a DCI format transmitted via the PDCCH.

[0057] [Table 4]

[0058] DCI format 0_0 is used to schedule a TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​is used to schedule a TB-based (or TB-level) PUSCH or a Code Block Group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 is used to schedule a TB-based (or TB-level) PDSCH, and DCI format 1_1 is used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH. DCI formats 0_0 / 0_1 are referred to as UL grant DCI or UL scheduling information, and DCI formats 1_0 / 1_1 are referred to as DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to convey dynamic slot format information (e.g., dynamic SFI) to a UE, and DCI format 2_1 is used to convey downlink pre-emption information to a UE. DCI format 2_0 and / or DCI format 2_1 are transmitted to terminals in a corresponding group via a group common PDCCH, which is a PDCCH transmitted to terminals defined in one group.

[0059] DCI format 0_0 and DCI format 1_0 are called fallback DCI formats, and DCI format 0_1 ​​and DCI format 1_1 are called non-fallback DCI formats. The fallback DCI format maintains the same DCI size / field configuration regardless of the terminal settings. On the other hand, the non-fallback DCI format has different DCI size / field configuration depending on the terminal settings.

[0060] The PDSCH carries downlink data (e.g., DL-SCH transport block, DL-SCH TB) and uses modulation methods such as QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), 64QAM, and 256QAM. The TB is encoded to generate a codeword. The PDSCH carries up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword are mapped to one or more layers. Each layer is mapped to resources along with a Demodulation Reference Signal (DMRS) to generate an OFDM symbol signal, which is then transmitted from the corresponding antenna port.

[0061] The PUCCH carries UCI (Uplink Control Information), which includes:

[0062] Scheduling Request (SR): Information used to request UL-SCH resources.

[0063] HARQ-ACK: A response to a downlink data packet (e.g., a codeword) on a PDSCH. It indicates whether the downlink data packet has been successfully received. One HARQ-ACK bit is transmitted as a response to a single codeword, and two HARQ-ACK bits are transmitted as a response to two codewords. HARQ-ACK responses include positive ACK (simply referred to as ACK), negative ACK (hereinafter referred to as NACK), DTX (Discontinuous Transmission), or NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0064] CSI (Channel State Information): Feedback information for a downlink channel. MIMO (Multiple Input Multiple Output)-related feedback information includes a Rank Indicator (RI) and a Precoding Matrix Indicator (PMI).

[0065] Table 5 shows an example of a PUCCH format, which can be divided into Short PUCCH (formats 0 and 2) and Long PUCCH (formats 1, 3, and 4) according to the PUCCH transmission length.

[0066] [Table 5]

[0067] PUCCH format 0 carries UCI with a maximum size of 2 bits and is mapped and transmitted based on a sequence. Specifically, a terminal transmits one of multiple sequences via a PUCCH with PUCCH format 0 to transmit specific UCI to a base station. The terminal transmits a PUCCH with PUCCH format 0 within a PUCCH resource for the corresponding SR setting only when transmitting a positive SR. PUCCH format 1 carries UCI with a maximum size of 2 bits, and modulation symbols are spread in the time domain by an orthogonal cover code (OCC) (which is set differently depending on whether frequency hopping is performed). DMRS is transmitted in symbols without modulation symbols (i.e., transmitted using time division multiplexing (TDM)).

[0068] PUCCH format 2 carries UCI with a bit size greater than 2 bits, and modulation symbols are transmitted using frequency division multiplexing (FDM) with DM-RS. DM-RS is located at symbol indices #1, #4, #7, and #10 within a 1 / 3 density resource block. A pseudo noise (PN) sequence is used for the DM-RS sequence. Frequency hopping can be enabled for the 2-symbol PUCCH format 2.

[0069] PUCCH format 3 does not multiplex terminals within the same physical resource block and carries UCI with a bit size greater than 2 bits. That is, the PUCCH resources of PUCCH format 3 do not include orthogonal cover codes. Modulation symbols are transmitted using DMRS and TDM (Time Division Multiplexing).

[0070] PUCCH format 4 supports multiplexing of up to four UEs in the same physical resource block and carries UCI with a bit size greater than 2. That is, the PUCCH resource of PUCCH format 3 includes an orthogonal cover code. Modulation symbols are transmitted using DMRS and TDM (Time Division Multiplexing).

[0071] The PUSCH carries uplink data (e.g., UL-SCH transport block, UL-SCH TB) and / or uplink control information (UCI) and is transmitted based on a cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveform or a discrete fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform. When the PUSCH is transmitted based on the DFT-s-OFDM waveform, the terminal applies transform precoding to transmit the PUSCH. For example, if transform precoding is not possible (e.g., transform precoding is disabled), the terminal transmits the PUSCH based on the CP-OFDM waveform, and if transform precoding is possible (e.g., transform precoding is enabled), the terminal transmits the PUSCH based on the CP-OFDM waveform or the DFT-s-OFDM waveform. PUSCH transmissions are dynamically scheduled by UL grants in DCI or semi-statically scheduled (configured grant) based on higher layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)). PUSCH transmissions can be codebook-based or non-codebook-based.

[0072] Figure 5 illustrates an ACK / NACK transmission process. Referring to Figure 5, a UE detects a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and the PDCCH indicates a DL allocation-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0, 1_1 include the following information:

[0073] Frequency domain resource assignment: Indicates the RB set allocated to the PDSCH.

[0074] -Time domain resource assignment: K0 (e.g., slot offset), indicating the start position of the PDSCH within slot #n+K0 (e.g., OFDM symbol index) and the length of the PDSCH (e.g., number of OFDM symbols)

[0075] -PDSCH-to-HARQ_feedback timing indicator: Indicates K1

[0076] -HARQ process number (4 bits): Indicates the HARQ process ID (Identity) for data (e.g., PDSCH, TB)

[0077] Thereafter, the UE receives the PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and then transmits UCI via the PUCCH in slot #(n1+K1) after finishing receiving the PDSCH in slot #n1 (where n+K0≦n1). Here, the UCI includes a HARQ-ACK response to the PDSCH. For convenience, in FIG. 5, it is assumed that the SCS for the PDSCH and the SCS for the PUCCH are the same and that slot #n1 = slot #n+K0, but the present invention is not limited to this. If the SCSs are different, K1 is indicated / interpreted based on the SCS of the PUCCH.

[0078] If the PDSCH is configured to transmit a maximum of one TB, the HARQ-ACK response consists of 1 bit. If the PDSCH is configured to transmit a maximum of two TBs, the HARQ-ACK response consists of 2 bits if spatial bundling is not configured, and 1 bit if spatial bundling is configured. If the transmission time of the HARQ-ACK for multiple PDSCHs is specified as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes the HARQ-ACK responses for multiple PDSCHs.

[0079] Whether or not a UE performs spatial bundling for HARQ-ACK responses is configured for each cell group (e.g., RRC / higher layer signaling). For example, spatial bundling is configured individually for each HARQ-ACK response transmitted via a PUCCH and / or a HARQ-ACK response transmitted via a PUSCH.

[0080] Spatial bundling is supported when the maximum number of TBs (or codewords) that can be received at one time (or scheduled by 1 DCI) in a corresponding serving cell is two (or more than two) (e.g., when the upper layer parameter maxNrofCodeWordsScheduledByDCI corresponds to 2-TB). On the other hand, for 2-TB transmission, more than four layers are used, and for 1-TB transmission, up to four layers are used. As a result, when spatial bundling is configured for a corresponding cell group, spatial bundling is performed on serving cells in the corresponding cell group that can schedule more than four layers. A UE that wishes to transmit a HARQ-ACK response via spatial bundling in a corresponding serving cell can generate a HARQ-ACK response by performing a bit-wise logical AND operation on A / N bits for multiple TBs.

[0081] For example, assuming that a terminal receives DCI scheduling 2-TB and receives 2-TB via PDSCH based on the DCI, a terminal performing spatial bundling can generate a single A / N bit by logically ANDing the first A / N bit for the first TB and the second A / N bit for the second TB. As a result, if both the first TB and the second TB are ACK, the terminal reports an ACK bit value to the base station, and if both TBs are NACK, the terminal reports a NACK bit value to the base station.

[0082] For example, if only 1-TB is actually scheduled on a serving cell configured to receive 2-TB, the terminal can generate a single A / N bit by logically ANDing the A / N bit for the 1-TB with a bit value of 1. As a result, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0083] A base station / UE has multiple parallel DL HARQ processes for DL ​​transmission. Multiple parallel HARQ processes enable continuous DL transmission while waiting for HARQ feedback for successful or unsuccessful reception of previous DL transmission. Each HARQ process is associated with a HARQ buffer in the Medium Access Control (MAC) layer. Each DL HARQ process manages state variables related to the number of transmissions of MAC Physical Data Blocks (PDUs) in the buffer, HARQ feedback for MAC PDUs in the buffer, the current redundancy version, etc. Each HARQ process is distinguished by a HARQ process ID.

[0084] 6 illustrates a PUSCH transmission process. Referring to FIG. 6, a UE detects a PDCCH in slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI formats 0_0 and 0_1). DCI formats 0_0 and 0_1 include the following information:

[0085] Frequency domain resource assignment: Indicates the RB set allocated to the PUSCH.

[0086] Time domain resource assignment: Indicates the slot offset K2, the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of the PUSCH within the slot. The starting symbol and length are indicated by the SLIV (Start and Length Indicator Value), or are indicated separately.

[0087] Thereafter, the terminal transmits a PUSCH in slot #(n+K2) according to the scheduling information of slot #n, where the PUSCH includes a UL-SCH TB.

[0088] Figure 7 shows an example of multiplexing USI into PUSCH. When multiple PUCCH resources and PUSCH resources overlap within a slot and simultaneous PUCCH-PUSCH transmission is not configured, UCI is transmitted via PUSCH as shown (UCI piggyback or PUSCH piggyback). Figure 7 illustrates a case where HARQ-ACK and CSI are included in PUSCH resources.

[0089] Configured Grant (CG)

[0090] A semi-static configured grant (CG) is configured in the UE by the higher layer (RRC). Up to 12 active CGs can be configured in the UE for the corresponding BWP of the serving cell.

[0091] Each CG is either Type 1 or Type 2. In Type 1 CG, all parameters for UL (e.g., PUSCH) transmission are signaled via higher layers. In Type 2 CG, some parameters for UL transmission are signaled by higher layers, and others are signaled by PDCCH (e.g., DCI format 0_1 ​​in Table 4). Activation / deactivation of Type 1 CG is performed independently between serving cells. Activation / deactivation of Type 2 CG is performed by DCI carried by PDCCH with CRC scrambled in CS (Configured Scheduling)-RNTI. When multiple Type 2 CGs are configured, activation of each Type 2 CG is performed individually by DCI. One DCI can deactivate one Type 2 CG or multiple Type 2 CGs.

[0092] For CG-based transmission on NR-U (i.e., shared spectrum channel access), Configured Grant Uplink control information (CG-UCI) is transmitted on the corresponding CG PUSCH (i.e., PUSCH scheduled by configured grant). On NR-U, multiplexing between CG-UCI and PUCCH carrying HARQ-ACK is configured / allowed by the base station. When multiplexing between CG-UCI and PUCCH carrying HARQ-ACK is not configured and the PUCCH carrying HARQ-ACK overlaps with the CG PUSCH within the PUCCH group, transmission of the CG PUSCH is omitted.

[0093] Repetition may be configured for CG PUSCH transmission; specifically, PUSCH repetition type A or PUSCH repetition type B is configured. In PUSCH repetition type A, the Kth CG PUSCH is repeated in K consecutive slots (i.e., one PUSCH is mapped to each slot). In PUSCH repetition type A, the number of nominal repetitions and the time resource of the first nominal repetition are instructed to the terminal, and the terminal performs actual repetitions based on the instructed number of nominal repetitions. The number of actual repetitions may be greater than or equal to the nominal repetitions. For example, the time resource of the subsequent nominal repetitions is determined from the time resource of the nominal repetition instructed to the terminal. However, if there is a DL resource in the middle of the nominal repetition or if the nominal repetition straddles a slot boundary, the nominal repetition is divided into multiple actual repetitions in the time domain.

[0094] NR-shared spectrum / unlicensed band(NR-U) operation

[0095] Figure 8 illustrates a wireless communication system that supports unlicensed bands. For convenience, a cell operating in a licensed band (hereinafter, L-band) is defined as an LCell, and a carrier of the LCell is defined as a (DL / UL) LCC (Licensed Component Carrier). Also, a cell operating in an unlicensed band (hereinafter, U-band) is defined as a UCell, and a carrier of the UCell is defined as a (DL / UL) UCC (Unlicensed Component Carrier). The carrier of a cell refers to the operating frequency (e.g., center frequency) of the cell. A cell / carrier (e.g., Component Carrier, CC) is collectively referred to as a cell.

[0096] When carrier aggregation (CA) is supported, a terminal can transmit and receive signals to and from a base station via multiple aggregated cells / carriers. When multiple CCs are configured in a terminal, one CC is configured as a PCC (Primary CC) and the remaining CCs are configured as SCCs (Secondary CCs). Specific control information / channels (e.g., CSS PDCCH, PUCCH) are configured to be transmitted and received only via the PCC. Data is transmitted and received via the PCC / SCC. Figure 8(a) illustrates an example in which a terminal and a base station transmit and receive signals via an LCC and a UCC (non-standalone (NSA) mode). In this case, the LCC is configured as a PCC and the UCC is configured as an SCC. When multiple LCCs are configured in a terminal, one specific LCC is configured as a PCC and the remaining LCCs are configured as SCCs. Figure 8(a) corresponds to LAA in a 3GPP LTE system. Figure 8(b) illustrates an example in which a UE and a base station transmit and receive signals via one or more UCCs without an LCC (SA (Standalone) mode). In this case, one of the UCCs is configured as a PCC, and the remaining UCCs are configured as SCCs. As a result, the NR UCell supports PUCCH, PUSCH, and PRACH transmission. Both NSA mode and SA mode are supported in the unlicensed band of the 3GPP NR system.

[0097] Unless otherwise stated, the following definitions apply to terms used in this specification.

[0098] Channel: Consists of consecutive RBs in which a channel access process is performed in a shared spectrum, and refers to a carrier or a portion of a carrier.

[0099] -Channel Access Procedure (CAP): A procedure for evaluating channel availability based on sensing to determine whether other communication nodes are using the channel before transmitting a signal. The basic unit for sensing is Tsl The sensing slot has a duration of 9 us. The base station or the terminal senses the channel during the sensing slot, and the power detected for at least 4 us within the sensing slot is equal to or exceeds the energy detection threshold X Thresh If it is smaller, the sensing slot period T sl is considered to be idle. Otherwise, the sensing slot period T sl =9us is considered busy. CAP is also known as LBT (Listen-Before-Talk).

[0100] Channel occupancy: refers to the corresponding transmission on the channel by the base station / terminal after the channel access procedure.

[0101] -Channel Occupancy Time (COT): Refers to the total time that the base station / terminal and any base station / terminal sharing the channel occupancy can transmit on the channel after the base station / terminal performs the channel connection process. When determining the COT, if the transmission gap is 25us or less, the gap period is also counted in the COT. The COT is shared for transmission between the base station and the corresponding terminal.

[0102] DL transmission burst: Defined as a set of transmissions from a base station with no gaps greater than 16 us. Transmissions from a base station separated by gaps greater than 16 us are considered individual DL transmission bursts. The base station does not sense channel availability within a DL transmission burst and transmits after the gap.

[0103] UL transmission burst: Defined as a set of transmissions from a terminal with no gaps greater than 16 us. Transmissions from a terminal separated by gaps greater than 16 us are considered individual UL transmission bursts. The terminal does not sense channel availability within a UL transmission burst and transmits after the gap.

[0104] Detection burst: refers to a DL transmission burst that includes a set of signals and / or channels that are confined within a (time) window and associated with a duty cycle. In an LTE-based system, a detection burst is a transmission initiated by a base station and includes PSS, SSS, and CRS (cell-specific RS), as well as a non-zero-power CSI-RS. In an NR-based system, a detection burst is a transmission initiated by a base station and includes at least an SS / PBCH block, as well as a CORESET for a PDCCH that schedules a PDSCH with SIB1, a PDSCH carrying SIB1, and / or a non-zero-power CSI-RS.

[0105] FIG. 9 illustrates a method for occupying resources in an unlicensed band. According to regional regulations for unlicensed bands, a communication node in an unlicensed band must determine whether other communication nodes are using the channel before transmitting a signal. Specifically, before transmitting a signal, the communication node can first perform carrier sensing (CS) to determine whether other communication nodes are transmitting signals. A clear channel assessment (CCA) is defined as being confirmed when it is determined that other communication nodes are not transmitting signals. If a CCA threshold is set, either predefined or via higher layer (e.g., RRC) signaling, the communication node determines the channel state as busy if energy higher than the CCA threshold is detected on the channel; otherwise, it determines the channel state as idle. For reference, the Wi-Fi standard (802.11ac) specifies the CCA threshold as -62 dBm for non-Wi-Fi signals and -82 dBm for Wi-Fi signals. If the channel state is determined to be idle, the communication node can begin transmitting signals on the UCell. The above series of processes is called LBT (Listen-Before-Talk) or CAP (Channel Access Procedure). LBT and CAP can be used interchangeably.

[0106] In Europe, two LBT operations are exemplified, called FBE (Frame based equipment) and LBE (Load Based Equipment).

[0107] 10, in the FBE-based LBT method, a fixed frame interval is made up of a channel occupancy time (e.g., 1-10 ms), which refers to the time a communication node can continue transmitting when it successfully connects to a channel, and an idle interval corresponding to at least 5% of the channel occupancy time. CCA is defined as the operation of monitoring the channel during a CCA slot (minimum 20 μs) at the end of the idle interval. A communication node periodically performs CCA in fixed frame units, and if the channel is unoccupied, it transmits data during the channel occupancy time. If the channel is occupied, it suspends transmission and waits for the CCA slot of the next period.

[0108] Referring to Figure 11, in the LBE-based LBT method, a communication node first sets a value of q ∈ {4, 5, ..., 32} and then performs CCA for one CCA slot. If the channel is unoccupied in the first CCA slot, it can reserve a time of up to (13 / 32)q ms to transmit data. If the channel is occupied in the first CCA slot, the communication node randomly selects a value of N ∈ {1, 2, ..., q} and stores it as the initial value of a counter. Thereafter, while sensing the channel state for each CCA slot, if the channel is unoccupied for that CCA slot, it decrements the value stored in the counter by one. When the counter value reaches 0, the communication node reserves a time of up to (13 / 32)q ms to transmit data.

[0109] Table 6 illustrates the channel access procedure (CAP) supported in NR-U.

[0110] [Table 6]

[0111] Meanwhile, Type 1 CAP is called Category 4 (CAT4)-LBT in the 3GPP standardization process, Type 2A CAP and Type 2B CAP are called CAT2-LBT in the 3GPP standardization process, and Type 2C CAP is called CAT1-LBT in the 3GPP standardization process. CAT2-LBT (i.e., Type 2A CAP and Type 2B CAP) is an FBE-based LBT, and CAT4-LBT is an LBE-based LBT.

[0112] Referring to Table 6, the base station performs one of the following channel access procedures (CAP) for downlink signal transmission in the unlicensed band.

[0113] (1) Type 1 Downlink (DL) CAP

[0114] In Type 1 DL CAP, the length of the time interval spanned by the sensing slots sensed as idle before transmission is random. Type 1 DL CAP is applied to the following transmissions:

[0115] a base station initiated transmission including (i) a unicast PDSCH with user plane data, or (ii) a unicast PDSCH with user plane data and a unicast PDCCH scheduling user plane data, or

[0116] - Base station initiated transmissions, which may either (i) have a detection burst only, or (ii) have a detection burst multiplexed with non-unicast information.

[0117] Referring to FIG. 12, the type 1 DL CAP in Table 6 will be described in more detail. First, the base station sets a delay duration T dDuring the sensing slot period, the channel is sensed to determine whether it is idle, and then, when the counter N reaches 0, transmission is performed (S1234). At this time, the counter N is adjusted by sensing the channel during the additional sensing slot period according to the following procedure:

[0118] Step 1) (S1220) N=N init where N init is 0 to CW p Then go to step 4.

[0119] Step 2) (S1240) If N>0 and the base station chooses to decrease the counter, set N=N-1.

[0120] Step 3) (S1250) Sense the channel during the additional sensing slot period. If the additional sensing slot period is idle (Y), proceed to step 4. If not (N), proceed to step 5.

[0121] Step 4) (S1230) If N=0 (Y), end the CAP procedure (S1232). Otherwise (N), go to step 2.

[0122] Step 5) (S1260) Additional delay period T d If a busy sensing slot is detected within the additional delay period T d Senses the channel until all sensing slots in are detected as idle.

[0123] Step 6) (S1270) Additional delay period T d If the channel is sensed idle during all sensing slot periods (Y), go to step 4. Otherwise (N), go to step 5.

[0124] (2) Type 2 DL CAP

[0125] In Type 2A / 2B DL ​​CAP, if the channel is sensed as idle for at least 25 us of the sensing period, the base station can transmit downlink in the unlicensed band immediately after the sensing period ends. In Type 2C DL CAP, the base station can access the channel immediately without sensing.

[0126] As shown in Table 6, multiple CAP Types (i.e., LBT Types) can be defined for uplink transmission in unlicensed bands. For example, Type 1 or Type 2 CAP is defined for uplink transmission. The UE can perform a CAP (e.g., Type 1 or Type 2) configured / instructed by the base station for uplink signal transmission.

[0127] (1) Type 1 Uplink CAP

[0128] Referring to FIG. 13, the Type 1 UL CAP in Table 6 will be described in more detail. The UE starts CAP for signal transmission through the unlicensed band (S1510). The UE randomly selects a backoff counter N within the contention window (CW) in step 1. At this time, the value of N is the initial value N init (S1520). init is 0 or CW pIf the backoff counter value (N) is 0 in step 4 (S1530; Y), the UE terminates the CAP procedure (S1532). The UE then performs Tx burst transmission (S1534). On the other hand, if the backoff counter value is not 0 (S1530; N), the UE decrements the backoff counter value by 1 in step 2 (S1540). The UE then checks whether the channel of the UCell(s) is idle (S1550). If the channel is idle (S1550; Y), the UE checks whether the backoff counter value is 0 (S1530). Conversely, if the channel is not idle in step S1550, i.e., if the channel is busy (S1550; N), the UE sets a defer duration T longer than the slot time (e.g., 9 us) in step 5. d It is checked whether the channel is idle during the delay period (S1560). If the channel is idle during the delay period (S1570; Y), the terminal restarts the CAP process. Here, the delay period is 16 usec and the immediately following m p The delay period consists of consecutive slot times (e.g., 9 us). On the other hand, if the channel is busy during the delay period (S1570; N), the terminal repeats step S1560 to check whether the channel is idle during the new delay period.

[0129] Table 7 shows the m applied to CAP by channel connection priority class (p). p , minimum CW(CW min,p ), maximum CW (CW max,p ), Maximum Channel Occupancy Time (MCOT) (T ulmCOT,p ) and allowed CW sizes are varied.

[0130] [Table 7]

[0131] The CWS size (CWS) applied to Type1 CAP is determined based on various methods. For example, the CWS is adjusted based on whether or not a New Data Indicator (NDI) value for at least one HARQ processor associated with HARQ_ID_ref, which is a HARQ process ID of the UL-SCH, toggles within a certain time interval (e.g., a reference time unit). When a terminal transmits a signal using Type1 CAP associated with channel access priority class p on a carrier, the terminal adjusts the CWS size for all priority classes p∈{1, 2, 3, 4} when the NDI value for at least one HARQ process associated with HARQ_ID_ref toggles. p =CW min,p otherwise, for all priority classes p∈{1, 2, 3, 4}, CW p to the next higher allowed value. Reference subframe n ref (or reference slot n ref ) is determined as follows:

[0132] The terminal is in subframe (or slot) n g UL grant is received in subframe (or slot) n 0、 n 1、…、 n w If a transmission including a gapless UL-SCH is made starting from subframe (or slot) n0 in ref is subframe (or slot) n0.

[0133] (2) Type 2 UL CAP

[0134] At least the sensing period T short_ul If the channel is sensed as idle during T = 25 us, the terminal can perform uplink transmission (e.g., PUSCH) in the unlicensed band immediately after the sensing ends. short_ul is T sl (=9us)+T f(=16us).

[0135] FIG. 14 illustrates an example in which multiple LBT-SBs are included in an unlicensed band. Referring to FIG. 14, multiple LBT-SBs are included in the BWP of a cell (or carrier). An LBT-SB has, for example, a 20 MHz bandwidth. An LBT-SB is composed of multiple consecutive (P)RBs in the frequency domain, referred to as a (P)RB set. Although not shown, guard bands (GBs) are included between the LBT-SBs. Therefore, the BWP is composed of the following format: {LBT-SB#0 (RB set #0) + GB#0 + LBT-SB#1 (RB set #1 + GB#1) + ... + LBT-SB#(K-1) (RB set (#K-1))}. For convenience, the LBT-SB / RB index is set / defined to start from the lower frequency band and increase toward the higher frequency band.

[0136] UE / BS-initiated COT-based transmission operation for unlicensed band operation

[0137] To support FBE-based U-band (e.g., shared spectrum) operation, NR Rel-16 introduces a Fixed Frame Period (FFP) transmission structure starting from BS-initiated COT (e.g., Type 2A / 2B CAP). The main features are summarized as follows:

[0138] [Table 8]

[0139] As shown in Table 8, the length of the FFP period is configured (semi-statically) in the UE by higher layer signaling (e.g., RRC), and the term FFP used in this specification can be simply referred to as period or semi-static period. Furthermore, channel occupancy based on FFP is also referred to as semi-static channel occupancy. Meanwhile, Rel-17 considers the introduction of an FFP transmission structure starting from UE-initiated COT to support efficient URLLC services in an FBE-based U-band environment. To this end, an FBE transmission operation method that takes into account both UE-initiated COT and BS-initiated COT is proposed. Hereinafter, a DL signal refers to a specific DL signal. Hereinafter, a BS refers to, but is not limited to, a gNB, which is a base station in a 5G NR system.

[0140] [1] Operation based on UE DL signal detection behavior in FBE operating conditions

[0141] First, for UE-initiated COT and BS-initiated COT based FBE operations, the following UE / BS transmission operations are basically considered.

[0142] 1) The UE is configured with an FFP section starting from BS-initiated COT (hereinafter referred to as "FFP-g" or "BS FFP") and its start time information, and also with an FFP section starting from UE-initiated COT (hereinafter referred to as "FFP-u" or "UE FFP") and its start time information.

[0143] A. As a result, the FFP-g of the BS and the FFP-u set in multiple UEs are configured in a manner that overlaps with each other in time.

[0144] 2) The UE is configured to perform LBT immediately before the start of its FFP-u (for example, during 25-μsec, 9-μsec, or 16-μsec).

[0145] A. If the channel is determined to be idle as a result of the LBT, the UE starts transmitting the corresponding FFP-u from the UE-initiated COT.

[0146] i. Meanwhile, BS operation is specified such that only if the BS successfully detects a specific UL signal (e.g., PUSCH / PUCCH DMRS, PRACH, SRS) from the UE within such an FFP-u interval, can it perform DL transmission (in the form of shared-COT) within the same FFP-u interval.

[0147] B. Otherwise, if the channel is determined to be busy, the UE performs Rel-16 operations assuming an FFP-g transmission structure including BS-initiated COT (for the FFP-g interval including the FFP-u start point) (e.g., Table 8).

[0148] i. In detail, it is defined that the UE can transmit configured UL (e.g., PRACH, PUSCH) in the same FFP-g interval only if it successfully detects a specific DL signal from the BS in the corresponding FFP-g interval. If the UE fails to detect the DL signal in the corresponding FFP-g interval, the corresponding UL transmission may not be allowed.

[0149] 3) Alternatively, the UE operates to perform DL signal detection from the BS for the FFP-g interval located before the start of its own FFP-u (in the FFP-g interval including the start of its own FFP-u).

[0150] A. If DL signal detection fails, the UE operates to perform LBT just before the start of its FFP-u (e.g., during 25-μsec, 9-μsec, or 16-μsec interval),

[0151] i. If the channel is determined to be idle as a result of the LBT, the UE starts the corresponding FFP-u transmission from the UE-initiated COT.

[0152] ii. If the result of the corresponding LBT indicates that the channel is busy, the UE operation is specified so that the UE does not perform any transmission (and / or reception) for the corresponding FFP interval, or the UE performs Rel-16 operation assuming an FFP-g transmission structure including BS-initiated COT (e.g., Table 8).

[0153] B. If DL signal detection is successful, the UE performs Rel-16 operation assuming an FFP-g transmission structure including BS-initiated COT (e.g., Table 8).

[0154] C. For example, before starting transmission via FFP-u / UE-initiated COT configuration, the UE attempts DL signal detection based on the FFP-g located earlier in the time domain (including the start time of the corresponding FFP-u), and prioritizes the shared-COT based on the DL signal detection. For example, if the UE is able to share the earlier BS-initiated COT and can transmit its own UL signal via the BS-initiated COT, the UE-initiated COT configuration (and the associated LBT) may be omitted. The UE transmits its UL signal based on the shared earlier BS-initiated COT.

[0155] Meanwhile, in such FBE operating conditions, the following UE transmission operation methods are considered depending on the DL signal detection state from the BS.

[0156] 1) Problem situation

[0157] A. When a specific UE1 detects a DL signal from a BS within a specific FFP-g interval, whether the DL signal is transmitted based on a BS-initiated COT or whether the BS has performed DL transmission in the form of shared-COT based on the UE-initiated COT of another UE2 determines whether UE1 is allowed to transmit the configured UL resources (e.g., CG PUSCH, PRACH, PUCCH, SRS) configured within the corresponding FFP-g (after the detected DL signal) (if the DL is a BS-initiated COT transmission) or not (if the DL is a shared-COT transmission based on a UE-initiated COT). However, if the UE's decision on this matter does not match the BS's intention, it may violate rules related to FBE operation or cause certain interference situations. For example, although the BS actually performs DL transmission by sharing the UE-initiated COT of UE2, UE1 may mistakenly believe that the DL signal was transmitted based on the BS-initiated COT and perform UL transmission based on the configured UL resource set in the corresponding FFP-g, which may result in problems such as signal collision. If UE1 knew that the DL signal was transmitted based on the UE-initiated COT sharing of UE2, the UL transmission of UE1 would be mistakenly performed, which could lead to problems.

[0158] 2) Proposal 1

[0159] A. When the BS transmits a DL signal in the form of shared-COT based on the UE-initiated COT generated from UE2, if UE1's configured UL resource is set within its own FFP-g interval (which overlaps with or includes the transmission time of the corresponding DL signal), the BS is specified to operate as follows: Opt 1 / 2.

[0160] i. Opt 1: The BS is specified to configure / transmit the corresponding DL signal only with signals that are not to be received / detected by UE1 (i.e., the corresponding DL signal is not detected or determined as being transmitted based on BS-initiated COT from the perspective of UE1). The specified operation may be, but is not limited to, one of the following: (i) broadcast signals / channels cannot be transmitted; (ii) unicast signals / channels (e.g., UE-specific PDCCH / PDSCH) or UE group-common (GC) PDCCH / PDSCH (carrying control information / data) related to UE1 cannot be transmitted; (iii) unicast signals / channels (carrying control information / data) related to UE2 can be transmitted; and / or (iv) GC-PDCCH / PDSCH (carrying control information / data) not related to UE1 can be transmitted.

[0161] ii. Opt 2: The BS is configured to transmit the DL signal only with unicast signals / channels (carrying control information / data) related to the UE 2. For example, broadcast signals / channels and GC-PDCCH / PDSCH are prohibited from transmission.

[0162] B. As a similar operation method, the following i.Opt A to iv.Opt D will be described assuming that the BS transmits DL signals / channels in a shared-COT format based on the UE-initiated COT generated from UE2.

[0163] i.Opt A

[0164] 1. If (from the BS's perspective) within an FFP-g interval including the DL transmission time point (or within the corresponding FFP-g interval after the DL transmission time point) there are only UL resources configured or scheduled for UE2, or there are no UL resources configured or scheduled for any UE, then the DL signal / channel transmitted by the BS can be received by any UE without any restrictions on its reception target. For example, all (or at least a part) of the following can be transmitted on the DL signal / channel: a unicast PDCCH / PDSCH / signal for UE2, a unicast PDCCH / PDSCH / signal for UEs other than UE2, a specific UE group-common PDCCH / PDSCH / signal, and a broadcast PDCCH / PDSCH / signal.

[0165] 2. Otherwise, if there are UL resources configured / instructed to UEs other than UE 2 within the FFP-g interval including the DL transmission time point (or within the FFP-g interval after the DL transmission time point) (from the BS's perspective), the DL signal / channel transmitted by the BS is limited to be received only by UE 2. For example, only unicast PDCCH / PDSCH / signal for UE 2 can be transmitted on the DL signal / channel.

[0166] ii. Opt B

[0167] 1. If (from the BS's perspective) within the FFP-g interval including the DL transmission point (or the interval after the DL transmission point within the corresponding FFP-g interval) there are only UL resources configured or scheduled for UE2, or there are no UL resources configured / instructed for any UE, or there are only scheduled UL resources for which UE-initiated COT-based transmission is instructed by DCI for UEs other than UE2, then the DL signal / channel transmitted by the BS can be received by any UE without any restrictions on its reception target.

[0168] 2. Otherwise, if there are configured UL resources set for other UEs other than UE2 or scheduled UL resources instructed by DCI for BS-initiated COT-based transmission to other UEs within the FFP-g interval including the DL transmission time point (or the interval after the DL transmission time point within the corresponding FFP-g interval) (from the BS's perspective), the DL signal / channel transmitted by the BS is limited to be received only by UE2.

[0169] iii. Opt C

[0170] 1. If (from the BS's perspective) there are no UL resources configured / instructed to any UE within the FFP-g interval including the DL transmission point (or the interval after the DL transmission point within the corresponding FFP-g interval), the DL signal / channel transmitted by the BS can be received by any UE without any restrictions on its reception target.

[0171] 2. Otherwise, if (from the BS's perspective) there are UL resources configured / instructed to any UE within the FFP-g interval including the DL transmission time (or within the FFP-g interval after the DL transmission time), the DL signal / channel transmitted by the BS is limited to be received by UE2 only.

[0172] iv. Opt D: Regardless of whether a specific UL resource exists within the FFP-g interval including the DL transmission time (or within the FFP-g interval after the DL transmission time), the DL signal / channel transmitted by the BS is always limited to be received by UE2 only.

[0173] 3) Proposal 2

[0174] A. For configured UL resources (e.g., UL resources configured semi-statically / semi-persistently by RRC, etc., e.g., CG PUSCH, PRACH, PUCCH) and / or scheduled UL resources (e.g., UL resources dynamically indicated / scheduled by DCI, etc., e.g., PUSCH, PUCCH), the energy detection threshold (EDT) value used for LBT for the corresponding UL resource transmission is set differently depending on whether or not there is a (time) alignment between the FFP-u start point and the corresponding UL resource (e.g., start symbol).

[0175] i. For example, for UL resources that are (time) aligned with the FFP-u start point, the EDT is fixed to a specific single value (hereinafter referred to as "EDT_sh") (e.g., a value separately set by the BS) and used. For UL resources that are not (time) aligned with the FFP-u start point, the EDT is fixed to another specific single value (hereinafter referred to as "EDT_no_sh") (e.g., a value calculated based on the UE maximum transmit power, etc.), or the UE selects and applies at least one of multiple EDT values ​​(e.g., EDT_sh and EDT_no_sh) (and the UE signals the EDT it selected / applied to the BS via the corresponding UL resource). For example, when FFP-u is configured for a specific UE, EDT_sh is always configured for the corresponding UE. For example, if the base station allows FFP-u configuration for a specific UE, it is specified that the base station always signals EDT_sh to the specific UE.

[0176] ii. (As an example related to the above example) If the UE generates / configures a UE-initiated COT by UL transmission applying EDT_sh, the UE performs additional (configured) UL transmission within the FFP-u section starting from the corresponding UE-initiated COT (or such additional UL transmission based on the UE-initiated COT is allowed).

[0177] iii. (As an example related to the above example) When a BS receives a transmission on an UL resource based on EDT_sh from a UE, the BS performs a shared-COT type DL transmission (or such shared-COT type DL transmission is allowed) on the UL resource after the transmission (determining that the UL transmission is based on UE-initiated COT). When a BS receives a transmission on an UL resource based on EDT_no_sh from a UE, the BS does not perform a shared-COT type DL transmission (or such shared-COT type DL transmission is not allowed) on the UL resource after the transmission (determining that the UL transmission is based on UE-initiated COT).

[0178] 4) Proposal 3

[0179] A. For configured UL resources (e.g., CG PUSCH, PRACH, PUCCH) and / or scheduled UL resources (e.g., PUSCH, PUCCH), even if the FFP-u start time and the corresponding UL resource (e.g., start symbol) are aligned (in time), the EDT value used for the LBT for the corresponding UL resource transmission is set differently depending on whether the corresponding UL transmission is a UE-initiated COT-based transmission.

[0180] For example, in the case of UE-initiated COT-based UL transmission, the EDT is fixed to a specific single value (e.g., EDT_sh). In the case of BS-initiated COT-based shared-COT UL transmission, the EDT is fixed to another specific single value (e.g., EDT_no_sh), or a UE-selected EDT value from multiple EDT values ​​(e.g., EDT_sh and EDT_no_sh) is applied (and the UE signals the selected / applied EDT to the BS via the corresponding UL resource). (On the other hand, if FFP-u is configured for the UE, EDT_sh is always configured for the UE.)

[0181] ii. (As an example related to the above example) If the UE generates / configures a UE-initiated COT by UL transmission applying EDT_sh, the UE performs further (configured) UL transmission within the FFP-u interval starting from the corresponding UE-initiated COT (or additional UL transmission based on such UE-initiated COT is permitted).

[0182] iii. (As an example related to the above example) For a transmission from a UE on an UL resource to which EDT_sh is applied, the BS performs shared-COT type DL transmission (or allows such shared-COT type DL transmission) after the UL resource (determining that the transmission is based on UE-initiated COT). For a transmission from a UE on an UL resource to which EDT_no_sh is applied, the BS does not perform shared-COT type DL transmission (or does not allow such shared-COT type DL transmission) after the UL resource (does not determine that the transmission is based on UE-initiated COT).

[0183] 5) Proposal 4

[0184] A. For configured UL resources (e.g., CG PUSCH, PRACH, and / or PUCCH) and / or scheduled UL resources (e.g., PUSCH and / or PUCCH), when the FFP-u start time and the corresponding UL resource (e.g., start symbol) are aligned, the EDT value applied when the UE generates / configures the UE-initiated COT through the corresponding UL transmission is set / instructed by the BS to one of multiple EDT values ​​(e.g., EDT_sh and EDT_no_sh), or the UE selects and applies one of multiple EDT values ​​(e.g., EDT_sh and EDT_no_sh).

[0185] i. (As an example related to the above example) If the UE generates / configures a UE-initiated COT by UL transmission applying EDT_sh, the UE performs (configured) UL transmission within the FFP-u interval starting from the corresponding UE-initiated COT (or additional UL transmission based on such UE-initiated COT is allowed).

[0186] ii. (As an example related to the above example) When a UE generates / configures a UE-initiated COT by UL transmission with EDT_no_sh applied, the UE either performs additional (configured) UL transmission within the FFP-u section starting from the UE-initiated COT (or such UE-initiated COT-based additional UL transmission is allowed), or the UE does not perform additional (configured) UL transmission within the FFP-u section starting from the UE-initiated COT (or such UE-initiated COT-based additional UL transmission is not allowed).

[0187] iii. (As an example related to the above example) When a UE transmits an UL resource to which EDT_sh is applied, the BS performs a shared-COT type DL transmission after the UL resource (or such shared-COT type DL transmission is allowed), and when a UE transmits an UL resource to which EDT_no_sh is applied, the BS does not perform a shared-COT type DL transmission after the UL resource (or such shared-COT type DL transmission is not allowed).

[0188] [2] UE transmission to configured UL resources in FBE operating state

[0189] 1) Problem situation

[0190] A. The subsequent operations and effects differ depending on whether the configured UL resources (e.g., CG PUSCH, PRACH, and / or PUCCH) that are set to be aligned (e.g., start symbols) at the start of FFP-u are transmitted based on UE-initiated COT or in a shared-COT format based on BS-initiated COT (which is defined as "shared-BS COT" transmission for convenience).

[0191] B. If (for example, in a situation like Figure 15) a configured UL (hereinafter referred to as "C-UL") resource (for example, C-UL#1 in Figure 15) is transmitted assuming UE-initiated COT, transmission of another C-UL resource (C-UL#x) configured to overlap with the idle period (F5) of FFP-u (for example, FFP-u#1 in Figure 15) at the end of FFP-u is not allowed. On the other hand, if a BS-initiated COT is assumed and C-UL#1 is transmitted with shared-BS COT, transmission of another C-UL resource (C-UL#x) configured to overlap with the idle period (at the end of FFP-u#1 in Figure 15) of FFP-u (within the FFP-g (FFP-g#1 in Figure 15) period starting from the BS-initiated COT) is allowed (Case 1-1).

[0192] C. Also, in the same situation as above (as in Figure 15), if UE-initiated COT transmission is assumed / performed for C-UL#1, the BS is not permitted to transmit a DL signal so that it overlaps with the idle period (F5) of FFP-u at the end of FFP-u#1. However, if shared-BS COT transmission is assumed / performed for the corresponding C-UL#1, the BS is permitted to transmit a DL signal so that it overlaps with the idle period (F5) of FFP-u at the end of FFP-u#1 (Case 1-2).

[0193] D. On the other hand, in a situation like that shown in Figure 15, if shared-BS COT transmission is assumed / performed for C-UL#1 aligned at the start of FFP-u#1, transmission of C-UL#2 set in FFP-u#2 immediately after FFP-u#1 in which C-UL#1 is set is possible, even though it is within the FFP-g#1 interval including the C-UL#1.However, if UE-initiated COT transmission is assumed / performed for the C-UL#1, transmission of C-UL#2 is not allowed (because C-UL#1 is outside the set FFP-u#1 interval) (Case 2-1).

[0194] E. Also, in a situation like that of Figure 16, if shared-BS COT transmission is assumed / performed for C-UL#1 aligned with the start point of FFP-u#1, transmission of C-UL#3 configured outside the FFP-g#1 interval including the corresponding C-UL#1 is not allowed (even though the corresponding C-UL#1 is within the configured FFP-u#2 interval), whereas if UE-initiated COT transmission is assumed / performed for C-UL#1, C-UL#3 transmission is allowed (because the corresponding C-UL#1 is within the configured FFP-u#2 interval) (Case 2-2).

[0195] F. In a situation where the UE / BS's connection / continuation behavior differs depending on whether UE-initiated COT transmission or shared-BS COT transmission is assumed / performed for a specific C-UL resource aligned at the start of FFP-u as described above, if the UE fails to detect the DL signal transmitted by the BS for the purpose of generating a BS-initiated COT, or if the BS considers the UL signal transmitted by the UE for the purpose of generating a UE-initiated COT to be a shared-BS COT transmission, the UE / BS's transmission / reception performance may be degraded or behavior that violates FBE-related rules may occur.

[0196] 2) Proposal 1

[0197] A. For a specific C-UL resource (e.g., C-UL #3 in FIG. 16) configured within a specific FFP-u (e.g., FFP-u #2 in FIG. 16) that is not aligned with the start point of the corresponding FFP-u:

[0198] i. If the UE detects a DL signal based on a BS-initiated COT for an FFP-g (e.g., FFP-g#2 in Figure 16) that includes a C-UL#3 resource (this is limited to the case where the C-UL#3 resource does not overlap with the start point of the FFP-g), the UE operates to assume / perform shared-BS COT transmission for the C-UL#3 resource (regardless of whether the UE generated / configured a UE-initiated COT for the FFP-u (e.g., FFP-u#2 in Figure 16) to which the C-UL#3 resource is configured) (this is defined as "Operation 1").

[0199] ii. Or, if the UE fails to detect a DL signal based on BS-initiated COT for an FFP-g (FFP-g#2 in Figure 16) including the corresponding C-UL#3 resource (this is limited to the case where the corresponding C-UL#3 resource does not overlap with the start point of the corresponding FFP-g), and the UE generates / configures a UE-initiated COT for an FFP-u (FFP-u#2 in Figure 16) to which the corresponding C-UL#3 resource is configured, the UE operates to assume / perform UE-initiated COT transmission for the corresponding C-UL#3 resource (this is defined as "Operation 2").

[0200] iii. As another method, if the UE fails to detect a DL signal based on the BS-initiated COT for an FFP-g (FFP-g#2 in Figure 16) including the corresponding C-UL#3 resource (this is limited to the case where the corresponding C-UL#3 resource does not overlap with the start point of the corresponding FFP-g), the UE shall consider the corresponding C-UL#3 resource to be invalid and shall not perform any transmission operation for the corresponding C-UL#3 resource (this is defined as "Operation 3").

[0201] B. The operation according to Proposal 1 can be similarly applied to scheduled UL resources, but for example, "a specific C-UL resource configured in FFP-u" can be replaced with "a specific scheduled UL resource indicated in FFP-u", "FFP-u in which the corresponding C-UL resource is configured" can be replaced with "FFP-u in which the corresponding scheduled UL resource is indicated", and "C-UL resource" can be replaced with "scheduled UL resource".

[0202] C. On the other hand, if a C-UL resource configured in a form that is not aligned with the start point of an FFP-u is configured to overlap with the start point of a specific FFP-g, the UE is prescribed to determine that the C-UL resource is invalid and not perform transmission operations on the C-UL resource.

[0203] D. On the other hand, if scheduled UL resources that are not aligned with the start point of FFP-u are instructed to overlap with the start point of a specific FFP-g, the UE is specified to apply / perform "Operation 1" and / or "Operation 2" and / or "Operation 3".

[0204] 3) Proposal 2

[0205] A. In a situation where the BS has generated / configured a BS-initiated COT for a particular FFP-g (e.g., FFP-g#1 in Figure 15):

[0206] i. Only when the following operations are performed will the BS be able / allowed to transmit a DL signal that overlaps with the idle period of a specific FFP-u within the FFP-g period (the idle period (F5) at the end of FFP-u#1 in Figure 15), and if the following operations are not performed, the BS will not be allowed to transmit a DL signal that overlaps with the idle period (F5) of a specific FFP-u within the FFP-g period.

[0207] 1. The BS (detected by the UE by a BS-initiated COT transmission) transmits a DL signal at the start of FFP-g, or before the idle period of FFP-u (the idle period (F5) at the end of FFP-u#1 in Figure 15), or before the start of the FFP-u (FFP-u#1 in Figure 15) immediately before the idle period in question.

[0208] ii. Only when the following operations are performed, is the BS capable / allowed to transmit a DL signal so that it overlaps with the start point of a specific FFP-u (FFP-u#2 in Figure 15) within the FFP-g interval; if the following operations are not performed, the BS is not allowed to transmit a DL signal so that it overlaps with the start point of a specific FFP-u within the FFP-g interval.

[0209] 1. The BS can transmit DL signals at the start of FFP-g or before the start of FFP-u (FFP-u#2 in FIG. 15) (detected by the UE in a BS-initiated COT transmission).

[0210] 4) Proposal 3

[0211] A. In a situation where a UE generates / configures a UE-initiated COT for a specific FFP-u (e.g., FFP-u#2 in FIG. 16) by transmitting a specific C-UL resource (C-UL#1 in FIG. 16) configured to be aligned with the start time of the FFP-u:

[0212] i. If the start point of a specific FFP-g (FFP-g#2 in Figure 16) is included within the FFP-u interval, the UE is specified to detect the DL signal transmitted based on the BS-initiated COT for the corresponding FFP-g#2 (to determine whether the corresponding DL signal is being transmitted or not).

[0213] 1. If a DL signal is detected, the UE is specified to operate in a state assuming BS-initiated COT (e.g., assume / perform UL transmission in the form of shared-BS COT) for the section within the FFP-u section that overlaps with the corresponding FFP-g#2 section (or after the point of detection of the corresponding DL signal) (e.g., UL resources configured / scheduled within the corresponding section).

[0214] 2. Otherwise, if detection of the DL signal fails, the UE is specified to assume / perform UE-initiated COT-based UL transmission for the section within the FFP-u section that overlaps with the corresponding FFP-g#2 section (or after the point of detection of the corresponding DL signal) (e.g., at least for the C-UL resource), or to determine / assume that the C-UL resource configured within the corresponding section is invalid and not perform transmission operation for the corresponding C-UL resource.

[0215] ii. Or, if the start point of a specific FFP-g (FFP-g#2 in Figure 16) is included within the FFP-u interval, the UE is specified to consider the C-UL resources set within the FFP-u interval that overlap with the FFP-g#2 interval (or after the point of DL signal detection) to be invalid (regardless of whether a DL signal is detected by the FFP-g#2), and not to perform transmission operations on the C-UL resources.

[0216] iii. This specifies that the UE assumes / performs UE-initiated COT-based UL transmission (e.g., at least for C-UL resources) only for the section (from the start of the FFP-u section) up to the end of the FFP-u section and the end of the FFP-g section (or up to X μsec (e.g., X = 9, 16, or 25) from the start of the FFP-g section immediately following the corresponding FFP-g), whichever is earlier.

[0217] 1. Therefore, if the end of the FFP-g interval (or a point X μsec (e.g., X=9, 16, or 25) before the start of the FFP-g interval immediately following the corresponding FFP-g) is earlier than the end of the FFP-u interval, UE-initiated COT-based transmission is not possible for C-UL resources that belong to the FFP-u interval but are outside the FFP-g interval (or a point X μsec (e.g., X=9, 16, or 25) before the start of the FFP-g interval immediately following the corresponding FFP-g) (only shared-BS COT-type UL transmission based on detection of a DL signal transmitted with BS-initiated COT is possible for the corresponding C-UL resource).

[0218] B. Or, if the start point of a specific FFP-u (FFP-u#2 in FIG. 16) is included within a specific FFP-g (FFP-g#1 in FIG. 16) section, and a specific C-UL resource (e.g., C-UL#1 in FIG. 16) is configured to be aligned with the start point of the corresponding FFP-u#2:

[0219] i. If the C-UL#1 resource overlaps in time with a specific DL signal / channel configured for transmission within the FFP-g#1 interval (e.g., SSB (resource for SS / PBCH transmission) for broadcast transmission and / or a specific (e.g., CORESET with the lowest ID / index) (configured by MIB / SIB, etc.), the operation of generating a UE-initiated COT is not permitted depending on the transmission of the corresponding C-UL#1 resource.

[0220] 1. As a result, it is specified that only UL transmission in the form of shared-BS COT based on detection of a DL signal transmitted in BS-initiated COT is possible for the FFP-u#2 section (including the C-UL#1 resource).

[0221] 5) Proposal 4

[0222] A. For any C-UL resource configured to be aligned with the start of a specific FFP-u or for a specific C-UL resource (e.g., configured to allow / allow UE-initiated COT creation / configuration by the corresponding C-UL transmission):

[0223] i. If the time interval (e.g., DL-to-UL gap) between the start of the corresponding FFP-u or the start symbol of the corresponding C-UL and the immediately preceding DL signal detection time is secured to be equal to or greater than X μsec (e.g., X=9, 16, or 25) (or the time corresponding to the idle period set in the FFP-u), the UE can generate / configure a UE-initiated COT by transmitting the corresponding C-UL resource (i.e., it is specified that UE-initiated COT generation / configuration by transmitting the corresponding C-UL resource is possible / allowed).

[0224] ii. Otherwise, if the time interval (e.g., DL-to-UL gap) between the start of the corresponding FFP-u or the start symbol of the corresponding C-UL and the immediately preceding DL signal detection time is not secured for at least X μsec (e.g., X=9, 16, or 25) (or the time corresponding to the idle period set in the FFP-u), the UE cannot generate / configure a UE-initiated COT by transmitting the corresponding C-UL resource, and it is specified that only shared-BS COT type transmission is possible / allowed for the corresponding C-UL resource, or the corresponding C-UL resource is considered invalid and no transmission operation is performed for the corresponding C-UL resource.

[0225] B. On the other hand, for C-UL resources that are not configured to allow / permit UE-initiated COT generation / configuration (by the corresponding C-UL transmission), the UE is specified to only be able / allowed to transmit in the form of shared-BS COT for the corresponding C-UL resource.

[0226] 6) Proposal 5

[0227] A. For any or specific C-UL resources configured to be aligned with the start of FFP-u (e.g., configured to allow / allow UE-initiated COT creation / configuration):

[0228] i. If the time interval (e.g., DL-to-UL gap) between the start of the corresponding FFP-u or the start symbol of the corresponding C-UL and the immediately preceding DL signal detection time is secured to be equal to or greater than X μsec (e.g., X=9, 16, or 25) (or the time corresponding to the idle period set in the FFP-u), the UE can generate / configure a UE-initiated COT by transmitting the corresponding C-UL resource (i.e., it is specified that UE-initiated COT generation / configuration by transmitting the corresponding C-UL resource is possible / allowed).

[0229] ii. Otherwise, if (the corresponding C-UL resource is included in a specific FFP-g interval) the time interval (e.g., DL-to-UL gap) between the start of the corresponding FFP-u or the start symbol of the corresponding C-UL and the immediately preceding DL signal detection time is not secured for at least X μsec (e.g., X=9, 16, or 25) (or the time corresponding to the idle interval set in FFP-u), the UE cannot generate / configure a UE-initiated COT by transmitting the corresponding C-UL resource. In this case, it is specified that only shared-BS COT type transmission is possible / allowed for the corresponding C-UL resource, or the corresponding C-UL resource is considered invalid and no transmission operation is performed for the corresponding C-UL resource.

[0230] B. On the other hand, in the case of a C-UL resource configured to be aligned with the start point of an FFP-u that is not configured to allow / permit UE-initiated COT generation / configuration, the UE is specified to only be able / allowed to transmit in the form of shared-BS COT for the corresponding C-UL resource.

[0231] C. The operations in Proposal 5 can be applied to scheduled UL resources as well, but for example, "C-UL resources configured to be aligned with the start of FFP-u" can be replaced with "scheduled UL resources instructed to be aligned with the start of FFP-u", and "C-UL resources" can be replaced with "scheduled UL resources".

[0232] 7) Proposal 6

[0233] A. A specific FFP-u (boundary) set may or may not be configured for the UE. If a specific FFP-u set is configured for the UE:

[0234] i. Only shared-BS COT type transmission is possible / allowed for C-UL resources configured to be aligned with the start time of FFP-u belonging to a specific FFP-u set.

[0235] ii. For C-UL resources configured to be aligned with the start of an FFP-u that does not belong to a specific FFP-u set:

[0236] -Alt-1

[0237] 1. If the time interval (e.g., DL-to-UL gap) between the start of the corresponding FFP-u or the start symbol of the corresponding C-UL and the immediately preceding DL signal detection time is secured to be equal to or greater than X μsec (e.g., X=9, 16, or 25) (or the time corresponding to the idle period set in the FFP-u), the UE can generate / configure a UE-initiated COT by transmitting the corresponding C-UL resource (i.e., generation / configuration of a UE-initiated COT by transmitting the corresponding C-UL resource is possible / allowed).

[0238] 2. Otherwise, if (the corresponding C-UL resource is included in a specific FFP-g interval) the time interval (e.g., DL-to-UL gap) between the start of the corresponding FFP-u or the start symbol of the corresponding C-UL and the immediately preceding DL signal detection time is not secured for at least X μsec (e.g., X=9, 16, or 25) (or the time corresponding to the idle interval set in FFP-u), the UE cannot generate / configure a UE-initiated COT by transmitting the corresponding C-UL resource, and only shared-BS COT type transmission is possible / allowed for the corresponding C-UL resource, or the corresponding C-UL resource is considered invalid and the corresponding C-UL transmission operation is not performed.

[0239] -Alt-2

[0240] 1. If there is no DL signal detected (by the corresponding FFP-g interval) at the start of the corresponding FFP-u or before the start symbol of the corresponding C-UL (when the corresponding C-UL resource is included within a specific FFP-g interval), the UE can generate / configure a UE-initiated COT by transmitting the corresponding C-UL resource (i.e., generation / configuration of a UE-initiated COT by transmitting the corresponding C-UL resource is possible / allowed).

[0241] 2. Otherwise, if there is a DL signal detected (by the corresponding FFP-g interval) at the start of the corresponding FFP-u or before the start symbol of the corresponding C-UL (when the corresponding C-UL resource is included within a specific FFP-g interval), the UE considers the corresponding C-UL resource to be invalid and does not perform a transmission operation on the corresponding C-UL resource.

[0242] B. Otherwise, if a specific FFP-u set is not configured for the UE, apply Alt-1 or Alt-2 operations to the C-UL resources configured to be aligned with the start point of any FFP-u.

[0243] C. This operating method can be similarly applied to scheduled UL resources, and (as an example related to the above example) the above operating method can be applied by replacing "C-UL resources configured to be aligned with the start time of FFP-u" with "scheduled UL resources instructed to be aligned with the start time of FFP-u" and "C-UL resources" with "scheduled UL resources".

[0244] D. On the other hand, for a specific FFP-u(boundary) set, it is set in the following way:

[0245] i.Alt-a: Even radio frame number / index (e.g., 0) including the first FFP-u after the start (boundary) point, it is set (for example, in bitmap form) to (the whole or) a specific part of the FFP-u set belonging to the X msec (e.g., X = 20 or X = 10) interval, and the corresponding FFP-u set setting is applied equally to the X msec period.

[0246] ii.Alt-b: Even radio frame number / index (e.g., 0) including the first FFP-u after the start (boundary) point, it is set (for example, in bitmap form) to (the whole or) a specific part of the set of Y FFP-u, and the corresponding FFP-u set setting is applied to the period of the Y FFP-u interval in the same manner.

[0247] E. On the other hand, for a specific FFP-u set, either a single FFP-u set that applies to both configured UL resources and scheduled UL resources is configured in the UE, or individual FFP-u sets that apply to each of the configured UL resources and scheduled UL resources are configured.

[0248] [3] UL / DL transmission to idle sections of FFP sections during FBE operation

[0249] 1) Problem situation 1

[0250] A. The UE, for FFP-u initiated by its UE-initiated COT transmission:

[0251] -Case U1) UL transmission is not permitted in the idle section of the corresponding FFP-u,

[0252] -Case U2) UL transmission is allowed depending on the idle section of FFP-g included in the corresponding FFP-u section.

[0253] B. For FFP-g starting with a BS-initiated COT transmission, the UE shall:

[0254] -Case N1) UL transmission (based on shared-BS COT) is not permitted in the idle section of the corresponding FFP-g,

[0255] -Case N2) UL transmission (based on shared-BS COT) is allowed depending on the idle section of FFP-u included in the corresponding FFP-g section.

[0256] C. Meanwhile, in Case U2 (and / or Case N2), if there is a disagreement between the UE and the BS regarding the COT Initiator (e.g., whether it is the UE or the BS) at a given time, unexpected interference may occur between the UE and the BS (and / or between the UEs). While the interference can be easily controlled in the case of scheduled UL transmission by indicating the appropriate UL transmission time by the DCI, it is not easy to control the interference in the case of a specific configured UL (e.g., CG PUSCH) transmission.

[0257] 2) Proposal 1

[0258] A. Opt 1

[0259] In case of i.Case U2, UL transmission is permitted only for scheduled UL transmission, and UL transmission is not permitted for configured UL transmission.

[0260] 1. As a result, the UE performs the configuration and transmission of the configured UL resource while regarding the idle section of the FFP-g corresponding to Case U2 as an invalid resource for the configured UL transmission.

[0261] ii. Or, in Case U2, whether UL transmission is allowed or not is configured in the UE for configured UL transmission.

[0262] B. Opt 2

[0263] i. In Case N2, UL transmission (based on shared-BS COT) is permitted only for scheduled UL transmission, and UL transmission (based on shared-BS COT) is not permitted for configured UL transmission.

[0264] 1. As a result, the UE performs the configuration and transmission of the configured UL resource while regarding the idle section of the FFP-u corresponding to Case N2 as an invalid resource for the configured UL transmission.

[0265] ii. Or, in the case of Case N2, whether or not UL transmission (based on shared-BS COT) is allowed for the configured UL transmission is configured in the UE.

[0266] C. Opt 3

[0267] i. In Case U2 and Case N2, UL transmission is permitted only for scheduled UL transmission, and UL transmission is not permitted for configured UL transmission.

[0268] 1. As a result, the UE can perform configuration and transmission operations of configured UL resources while regarding the idle section of FFP-g corresponding to Case U2 and the idle section of FFP-u corresponding to Case N2 as invalid resources for configured UL transmission.

[0269] ii. Alternatively, in the cases of Case U2 and Case N2, whether UL transmission is permitted or not is configured in the UE for configured UL transmission.

[0270] D. Note: For configured UL, at least CG PUSCH is included.

[0271] 3) Problem situation 2

[0272] A. For FFP-g that begins with a BS-initiated COT transmission, the BS:

[0273] -Case A1) DL transmission through the idle section of the corresponding FFP-g is not permitted, but

[0274] -Case A2) DL transmission is permitted depending on the idle section of FFP-u included in the corresponding FFP-g section.

[0275] B. For FFP-u starting with a UE-initiated COT transmission, the BS:

[0276] -Case B1) DL transmission (based on shared-UE COT) is not allowed in the idle section of the corresponding FFP-u,

[0277] Case B2) DL transmission (based on shared-UE COT) is allowed depending on the idle section of FFP-g included in the corresponding FFP-u section.

[0278] C. Meanwhile, in Case A2 (and / or Case B2), if there is a mismatch between the UE and the BS regarding the COT initiator (e.g., whether it is the UE or the BS) at the relevant time, unexpected interference may occur between the UE and the BS (and / or between the UEs). While the interference effect is easily controlled in the case of scheduled DL transmission by indicating the appropriate DL transmission time point via DCI, it is not easy to control the interference effect in the case of a specific configured DL (e.g., SPS PDSCH) transmission.

[0279] 4) Proposal 2

[0280] A. Opt 1

[0281] In i.Case A2, it is specified that the UE performs DL reception only for scheduled DL transmissions, and does not perform DL reception for configured DL transmissions.

[0282] 1. As a result, the UE can perform the configuration and reception of configured DL resources while regarding the idle section of FFP-u corresponding to Case A2 as an invalid resource for configured DL transmission.

[0283] ii. Alternatively, in Case A2, whether to perform DL reception for configured DL transmission is configured in the UE.

[0284] B. Opt 2

[0285] In case of i.Case B2, the UE is specified to perform DL reception only for scheduled DL transmissions (based on the shared-UE COT) and not to perform DL reception for configured DL transmissions (based on the shared-UE COT).

[0286] 1. As a result, the UE can perform the configuration and reception of configured DL resources while regarding the idle section of FFP-g corresponding to Case B2 as an invalid resource for configured DL transmission.

[0287] ii. Or, in the case of Case B2, whether to perform DL reception for configured DL transmission (based on shared-UE COT) is configured in the UE.

[0288] C. Opt 3

[0289] i. In Case A2 and Case B2, it is specified that the UE performs DL reception only for scheduled DL transmissions and does not perform DL reception for configured DL transmissions.

[0290] 1. As a result, the UE can perform the configuration and reception operations of the configured DL resources while considering the idle interval of FFP-u corresponding to Case A2 and the idle interval of FFP-g corresponding to Case B2 as invalid resources for configured DL transmission.

[0291] ii. Alternatively, in the cases of Case A2 and Case B2, whether to perform DL reception for configured DL transmission is configured in the UE.

[0292] D. Note: For configured DL, at least SPS PDSCH is included.

[0293] [4] UE behavior for scheduled UL transmissions in FBE operating conditions

[0294] 1) In a situation where DCI indicates whether a scheduled UL (e.g., PUSCH, PUCCH) transmission should be transmitted based on UE-initiated COT or in a shared-COT format (based on BS-initiated COT), the following UE behaviors are possible:

[0295] A. When a scheduled UL (e.g., PUSCH / PUCCH / SRS) resource is instructed to a UE by an UL / DL scheduling DCI and the UE is instructed to transmit on the corresponding scheduled UL resource, for example, in a shared-COT format (e.g., a format in which scheduled UL is transmitted based on a BS-initiated COT within an FFP-g period), Opt 1) the UE transmits on the corresponding scheduled UL resource in a shared-COT format (omitting the DL signal detection / sensing process or regardless of the presence / result of DL signal detection) assuming that the BS has already started BS-initiated COT transmission for the FFP-g period including the scheduled UL resource, or Opt 2) the UE transmits on the corresponding scheduled UL resource only when it detects a DL signal (transmitted based on a BS-initiated COT) (as a result of performing a DL signal detection / sensing process) on the FFP-g including the corresponding scheduled UL resource. UL transmission is performed in the shared-COT format on the UL resource, and if DL signal detection fails (as a result of the DL signal detection / sensing process on the FFP-g including the corresponding scheduled UL resource), the corresponding scheduled UL transmission is dropped.

[0296] B. As an example of Opt 1 operation, when cell 1 where DCI is transmitted and cell 2 where scheduled UL resources are allocated are different from each other (e.g., when DCI on cell 1 is configured to cross-carrier schedule PUSCH on cell 2, and / or HARQ-ACK feedback for DCI / PDSCH transmission on cell 1 is transmitted via PUCCH on cell 2), and the time when DCI is transmitted is contained (confined) within the FFP-g interval (e.g., FFP-g on cell 2) where scheduled UL resources are allocated (or when the FFP-g interval on cell 1 including the DCI transmission time overlaps in time with the FFP-g interval on cell 2 including scheduled UL resources), the UE / BS transmits and receives UL signals based on Opt 1.

[0297] C. As an example of Opt 2 operation, when cell 1 where the DCI is transmitted is different from cell 2 where the scheduled UL resources are allocated, and (and / or) the time when the DCI is transmitted is not included in the FFP-g interval (e.g., FFP-g on cell 2) where the scheduled UL resources are allocated (or when the FFP-g interval on cell 1 including the DCI transmission time does not overlap in time with the FFP-g interval on cell 2 including the scheduled UL resources) (for convenience, this case is defined as "Case A"), the UE / BS transmits and receives UL signals based on Opt 2. (In a cross-carrier scheduling situation, DL signal detection to confirm that the BS has reserved / occupied the corresponding FFP-g (e.g., initiated by BS-initiated COT)) is performed on cell 2 where the scheduled UL resources are allocated. The application of Opt 2 operation is not necessarily limited to cross-carrier scheduling. As an example of Opt 2 operation, Opt 2 is also applied when the cell where the DCI is transmitted is the same as the cell where the scheduled UL resources are allocated. As an example, if the cell from which the DCI is transmitted and the cell to which the scheduled UL resource is allocated are the same, and the scheduled UL resource is not confined within the FFP-g from which the DCI is received, the UE / BS applies Opt 2.

[0298] D. In the case of Case A, if a specific (e.g., UE group-common) DCI indicates that the FFP-g interval on cell 2 to which UL resources are allocated is available for DL ​​transmission / reception, the operation of Opt 1 is applied as an exception.

[0299] 17 is a diagram illustrating UL signal transmission and reception according to one embodiment of the present invention. Meanwhile, as described above, in order to perform scheduled UL transmission in the shared-COT mode, the UE (in principle) needs to confirm that the BS has successfully occupied / secured the corresponding FFP-g (e.g., confirm that the BS initiated COT begins), and the UE can perform UL transmission by sharing the remaining FFP-g interval only after the BS has completed DL transmission in the FFP-g that the BS has successfully occupied / secured. However, (exceptionally) if it is determined that Opt 1 is applicable, the UE may omit the separate step (H20) of confirming that the BS has successfully occupied / secured the corresponding FFP-g.

[0300] Referring to FIG. 17, a UE receives a DCI (H10). The DCI schedules an UL transmission and may be, but is not limited to, an UL grant DCI. For example, since a UE's PUCCH transmission using a PUCCH resource indicated by the DL grant DCI is also a scheduled UL transmission, the DCI may be a DL grant DCI. Assume that the FFP from which the DCI is received is FFP_a. The FFP_a may be an FFP-g initiated from a BS-initiated COT. The DCI indicates channel access parameters for UL transmission. Based on the DCI, the UE determines whether the scheduled UL is related to an FFP-g (a BS-initiated COT corresponding to the FFP-g) or an FFP-u (a UE-initiated COT corresponding to the FFP-u). The UE determines whether to perform channel sensing for the scheduled UL based on network signaling, e.g., the DCI. Hereinafter, it is assumed that the UL transmission scheduled by the DCI is included in the FFP-g (starting from the BS initiated COT), and the UE is instructed to perform scheduled UL transmission in the shared-COT format on the FFP-g starting from the BS initiated COT.

[0301] The UE that has received the DCI checks whether the scheduled UL resource is included in the FFP_a in which the DCI is received (H15).

[0302] If the scheduled UL resource is included in FFP_a, i.e., if the scheduled UL is scheduled on the same FFP as the DCI (e.g., intra period scheduling), the UE performs scheduled UL transmission based on Opt 1 (H25). Scheduled UL transmission based on Opt 1 is performed based on the shared COT. In scheduled UL transmission based on Opt 1, the DL detection / sensing process for confirming that the corresponding FFP is FFP-g starting from the BS initiated COT is omitted. Figure 18 shows an example of a case where the UE performs UL transmission based on the shared COT. For example, Figure 18 relates to H25 or H30 in Figure 17. Referring to Figure 18, the UE determines whether the scheduled UL is performed within a maximum 16 us time gap from the previous UL transmission point (if there is a previous UL performed before the scheduled UL) (J15). For example, if there is a previous UL transmission within a maximum 16 us time gap from the corresponding scheduled UL, the UE performs the scheduled UL without a separate channel sensing (LBT) (J25). If there is no previous UL transmission within a maximum 16 us time gap from the corresponding scheduled UL, the UE performs a separate channel sensing (LBT) process (J20) and, if idleness is confirmed, performs the scheduled UL (J30).

[0303] Returning to FIG. 17, if the scheduled UL resource is not included in FFP_a, i.e., if the scheduled UL is scheduled on an FFP_b different from the DCI (e.g., cross period scheduling), the UE performs scheduled UL transmission based on Opt 2 (H15, No). According to Opt 2, the UE must perform DL detection / sensing procedures for the FFP_b to which the scheduled UL belongs (H20). At the time of FFP_a where the DCI is transmitted or received, the UE / BS cannot be sure whether FFP_b will be occupied by the BS in the future. This is because the corresponding frequency band is a shared spectrum / unlicensed band and must coexist with other devices / other standards (e.g., IEEE 802.11, etc.). For example, even if a 3GPP UE and a BS operating a serving cell agree in advance (e.g., at the latest at the time of FFP_a) that FFP_b will be set to FFP-g starting from the BS-initiated COT, it is still possible that a third device that does not comply with the 3GPP protocol or that is unaware of the prior agreement between the 3GPP UE and the BS may occupy at least a portion of FFP_b. For example, because the 3GPP BS / UE does not have the authority to monopolize the frequency band, it is not possible to completely eliminate the occupancy of a third device in FFP_b. Therefore, the UE must confirm whether the BS has actually successfully occupied the FFP_b at the start of the FFP_b to which the scheduled UL belongs. That is, it must perform a DL detection / sensing process to confirm whether a DL signal related to the BS-initiated COT exists at the start of the FFP_b (H20). If there is no DL signal related to the BS initiated COT at the start of FFP_b (H20, non-pass), the UE cannot be sure whether FFP_b is occupied by the BS (in other words, there is a possibility of channel occupation by a third device), so the UE does not transmit a scheduled UL that may collide with the third device (H25, Drop).If there is a DL signal related to the BS initiated COT at the start of FFP_b (H20, pass), the UE determines that FFP_b is occupied / reserved by the BS, and the UE transmits a scheduled UL based on the shared COT (H30 and Figure 18).

[0304] E. Meanwhile, not only the presence or absence of overlap between DCI and scheduled UL in the time domain (presence or absence of intra period), but also the presence or absence of overlap between DCI and scheduled UL in the frequency domain (presence or absence of intra freq.) is taken into consideration. Also, even when the cell from which (UL / DL grant) DCI is transmitted and the cell to which scheduled UL (e.g., PUSCH / PUCCH / SRS) resources are allocated are the same, the application of Opt 1 / 2 is taken into consideration.

[0305] For example, even if the transmitted cell and the cell to which the scheduled UL resource is allocated are the same, if one or more (multiple) RB sets (requiring individual / independent LBT) are configured on the corresponding cell, Opt 2 may be applied.

[0306] Alternatively, if the cell in which the DCI is transmitted is the same as the cell to which the scheduled UL resource is allocated, and one or more RB sets are configured on the corresponding cell, the application of the Opt 1 / 2 operation described above is classified as follows:

[0307] As an example of i.Opt 1 operation, when RB set 1 in which DCI is transmitted and RB set 2 to which the (corresponding) scheduled UL resource is allocated are different, and the DCI transmission and the scheduled UL resource are included in the same FFP-g period (i.e., intra period), the UE / BS operates based on Opt 1. For example, referring to (a) of FIG. 20, (even if RB set#a ≠ RB set#c), the UE / BS can transmit and receive UL signals based on Opt 1 based on the fact that the scheduled UL resource (indicated as being associated with the BS initiated COT) is included in the FFP-g#j period in which DCI is received. For example, referring to (b) of FIG. 20, (even if carrier#a≠carrier#b), the UE / BS can transmit and receive UL signals based on Opt 1 based on the fact that the scheduled UL resources (indicated as being related to the BS initiated COT) are completely contained within the FFP-g#x interval in which the corresponding DCI is received (e.g., the start and end of the scheduled UL resources are all completely contained within FFP-g#x).

[0308] ii. As an example of Opt 2 operation, even when the RB set to which a DCI is transmitted and the RB set to which the corresponding scheduled UL resource is allocated are the same (i.e., intra freq.), UL signal transmission and reception can be performed based on Opt 2. Opt 2 is not necessarily limited to DCI and scheduled UL resource in different RB sets. For example, when (the DCI and scheduled UL resource belong to different RB sets) the DCI transmission and the scheduled UL resource are not included in the same FFP-g period (i.e., included in different FFP-g periods) (e.g., cross period & cross freq.; hereinafter, this case is defined as "Case B" for convenience), the UE / BS operates based on Opt 2, and in this case, DL signal detection (e.g., H20a in FIG. 19) refers to DL signal detection on the RB set to which the scheduled UL resource is allocated.

[0309] iii. (Even in Case B) Opt 1 operation may be applied as an exception if the FFP-g interval on RB set 2 to which scheduled UL resources are allocated is indicated as useful for DL ​​transmission / reception by DCI of a specific format (e.g., UE group-common).

[0310] F. Figure 19 is a diagram for explaining UL signal transmission and reception according to an embodiment of the present invention. Figure 19 is an example in which the UL signal transmission and reception of Figure 17 described above is more specifically limited. That is, Figure 17 is a superordinate concept of Figure 19, and Figure 19 and Figure 17 are not mutually exclusive. Figure 19 is one embodiment of Figure 17, and the description of Figure 17 should not be construed as being limited by Figure 19. However, the description overlapping with Figure 17 will be omitted in Figure 19. A UE receives DCI (e.g., UL grant DCI or DL ​​grant DCI) scheduling UL transmission (H10a). Assume that the FFP in which the DCI is received is FFP_a. FFP_a may be FFP-g originating from the BS initiated COT. The DCI indicates channel access parameters for UL transmission. Based on the DCI, the UE determines whether the scheduled UL is related to an FFP-g (BS-initiated COT corresponding to the FFP-g) or an FFP-u (UE-initiated COT corresponding to the FFP-u). The UE determines whether to perform channel sensing for the scheduled UL based on network signaling, e.g., DCI. Hereinafter, it is assumed that the UL transmission scheduled by the DCI is included in an FFP-g (starting from the BS-initiated COT) and that the UE is instructed to perform scheduled UL transmission in the form of shared-COT on the FFP-g starting from the BS-initiated COT.

[0311] Upon receiving the DCI, the UE checks whether the scheduled UL resource is (completely) included in the FFP_a where the DCI was received (Intra period) and whether the scheduled UL resource is (completely) included in the frequency resource region (e.g., RB set or carrier) where the DCI was received (Intra Freq.) (H15a).

[0312] If the Intra period and Intra Freq. are met, the UE performs scheduled UL transmission based on Opt 1 (H25, FIG. 18). For example, in the same frequency resource region (RB set / carrier) and the same FFP-g, the UE / BS performs Opt 1-based operations (for example, if DCI is received in the RB set to which the UL resource is allocated, the DL signal detection process is omitted).

[0313] In the case of Cross period & Cross freq., the UE performs scheduled UL transmission based on Opt 2 (H15a, No).

[0314] In FIG. 18, the UE is exemplified as performing scheduled UL transmission based on Opt 2 when it is a cross period or a cross freq., but the present invention is not limited to this, and the UE may also operate as follows (hereinafter, i / ii can be understood as a result similar to the embodiment of FIG. 17 which does not distinguish between the presence or absence of cross / intra freq.).

[0315] i. For example, (in the case of Intra period & Cross freq. or Intra period & Same freq.), the UE can perform scheduled UL transmission based on the Intra period. If DCI is transmitted on frequency resource region #1 (e.g., RB set / carrier #1) and the DCI transmission time on frequency resource region #1 is included in the FFP-g interval on frequency resource region #2 (e.g., RB set / carrier #2) to which scheduled UL resources are allocated, Opt 1 is applied (here, RB set / carrier #1 and RB set / carrier #2 are the same or different RB sets / carriers).

[0316] ii. For example, (in the case of cross period & intra frequency or cross period & same frequency), the UE can perform scheduled UL transmission based on the cross period. When DCI is transmitted on frequency resource region #1 (e.g., RB set / carrier #1) and the DCI transmission time on frequency resource region #1 is not included in the FFP-g interval on frequency resource region #2 (e.g., RB set / carrier #2) to which scheduled UL resources are allocated (e.g., located before the start of the corresponding 3 FFP-g interval), Opt 2 is applied.

[0317] 2) In a situation where DCI indicates whether the UL transmission for a scheduled UL transmission should be transmitted based on UE-initiated COT or in the form of shared-COT (transmission form), the following UE behaviors may be further considered:

[0318] A. When UE-initiated COT-based transmission is instructed by DCI for a specific scheduled UL resource (e.g., a resource that is not aligned with the start of a specific FFP-u interval but is allocated to be included within the FFP-u interval), if the UE has already started UE-initiated COT transmission for the corresponding FFP-u interval at a previous point in time, the UE transmits the corresponding scheduled UL resource based on the UE-initiated COT; otherwise, the UE operates to drop transmission for the corresponding scheduled UL resource.

[0319] B. In addition, when shared-COT-based transmission is instructed by DCI for a specific scheduled UL resource (e.g., allocated to be included in a specific FFP-g interval), if the UE has already performed shared-COT transmission within the corresponding FFP-g interval at a previous point in time (omitting detection of another DL signal in the cell to which the corresponding scheduled UL resource is allocated, or regardless of whether a DL signal is detected in the corresponding cell), the corresponding scheduled UL resource is transmitted based on shared-COT; otherwise, Opt 1 or Opt 2 operation is applied (depending on the presence or absence of cross-carrier scheduling / instruction and the FFP-g interval for each cell, etc.).

[0320] [5] Handling operations related to the COT Initiator's decision in the FBE operating situation

[0321] In a situation where a carrier (i.e., a cell) consisting of multiple RB sets and / or multiple cells (consisting of one or more RB sets) are configured for a UE (i.e., CA), the following operations can be considered in relation to determining the COT Initiator (e.g., UE-initiated COT or BS-initiated COT) (from the UE's perspective).

[0322] A. For an RB set group consisting of multiple RB sets configured on the same cell (e.g., intra-carrier) or the same BWP (and / or a cell (RB set) group consisting of multiple cells (multiple RB sets configured in the corresponding cells) configured on the same frequency band (e.g., intra-band)), a BS-initiated COT (or UL transmission based on the BS-initiated COT (e.g., scheduled)) is indicated (by a specific (e.g., UE-specific or UE group-common) DCI) for a specific FFP-g interval, or a DL signal corresponding thereto (transmitted based on the BS-initiated COT) is detected, or (by a specific (e.g., UE In the case where there is no RB set indicated as useful for DL ​​transmission / reception (by (group-common or UE-specific) DCI) (or an RB set including a specific DL signal / channel (e.g., SSB (resources used for SS / PBCH transmission) where broadcast transmission is performed and / or a specific (e.g., CORESET with the lowest ID / index) (set by MIB / SIB, etc.))), it is permitted / possible to perform UL transmission based on UE-initiated COT using RB sets (all or part) belonging to the RB set group in an FFP-u interval that overlaps in time with the corresponding FFP-g interval or whose FFP start point is included in the corresponding FFP-g interval (and / or an FFP-u interval that overlaps in time with the start point of the corresponding FFP-g).

[0323] i. In this case, if the BS instructs a specific RB set belonging to an RB set group (for the FFP-u period) that it is UE-initiated COT (or that (e.g., scheduled) UL transmission is based on UE-initiated COT), or if the UE decides to assume UE-initiated COT (for a specific (e.g., configured) UL transmission assigned to the RB set), the UE operates to perform UL transmission using the RB set (or the RB set group to which this RB set belongs) while assuming / determining UE-initiated COT for the RB set (or the entire RB set group to which this RB set belongs).

[0324] B. For an RB set group consisting of multiple RB sets configured on the same cell (e.g., intra-carrier) or the same BWP (and / or a cell (RB set) group consisting of multiple cells (multiple RB sets configured in the corresponding cells) configured on the same frequency band (e.g., intra-band)), a BS-initiated COT (or UL transmission based on the BS-initiated COT (e.g., scheduled)) is indicated (by a specific (e.g., UE-specific or UE group-common) DCI) for a specific FFP-g interval, or a DL signal corresponding thereto (transmitted based on the BS-initiated COT) is detected, or (a specific (e.g., UE If there is at least one RB set (or an RB set including a specific DL signal / channel (e.g., an SSB (resources used for SS / PBCH transmission) on which broadcast transmission is performed and / or a specific (e.g., CORESET with the lowest ID / index) (set by MIB / SIB, etc.)) indicated as useful for DL ​​transmission / reception (by a DCI (group-common or UE-specific)), then it is not permitted / impossible to perform UL transmission based on UE-initiated COT by any RB set belonging to the RB set group in an FFP-u interval that overlaps in time with the corresponding FFP-g interval or whose FFP start point is included in the corresponding FFP-g interval (and / or an FFP-u interval that overlaps in time with the start point of the corresponding FFP-g) (thus, only UL transmission based on BS-initiated COT (shared-COT-based) is permitted / possible in the FFP-g interval).

[0325] i. In this case, if a specific RB set belonging to an RB set group (for the FFP-g interval) is instructed to be BS-initiated COT (or UL transmission based on BS-initiated COT (e.g., scheduled)), or a corresponding DL signal (transmitted based on BS-initiated COT) is detected, or is instructed to be useful for DL ​​transmission / reception, the UE operates to perform UL transmission using the corresponding RB set while assuming / determining BS-initiated COT only for the corresponding RB set.

[0326] C. In another method, for an RB set group consisting of multiple RB sets configured in the same cell (e.g., intra-carrier) or the same BWP (and / or a cell (RB set) group consisting of multiple cells (multiple RB sets configured in the corresponding cells) configured in the same frequency band (e.g., intra-band)):

[0327] When a guard band (e.g., intra-carrier) is configured between frequency-adjacent RB sets on a cell / BWP and a specific (allocated) RB set in the RB set group is configured / indicated as a specific type (e.g., configured or scheduled) UL transmission resource,

[0328] If the COT Initiator determined / assumed / instructed for the corresponding assigned RB set (e.g., UE-initiated COT or BS-initiated COT) matches, UL transmission is allowed / possible regardless of whether the COT Initiator matches the COT Initiator determined / assumed / instructed for the remaining RB sets (excluding the corresponding assigned RB set). For convenience, this behavior is defined as "multi-RB set behavior 1."

[0329] i. As an example, if the determined / assumed / instructed COT Initiator for the assigned RB set matches the UE-initiated COT, UL transmission is allowed / possible even if the determined / assumed / instructed COT Initiator for the remaining RB set is BS-initiated COT.

[0330] ii. Therefore, in this case, if the COT Initiator determined / assumed / indicated for the assigned RB set differs between the RB sets, UL transmission is not allowed / impossible (i.e., the UE operates to omit the corresponding UL transmission).

[0331] iii. As a specific example, assume that an RB set group including a total of N RB sets is configured (on a BWP or carrier), and the UE performs UL transmission using M (an integer less than or equal to N) RB sets in the corresponding RB set group. Meanwhile, the COT Initiator is determined for each RB set. (i) When the UL transmission performed by the UE corresponds to a configured UL, if it is not determined that the COT Initiators of the M RB sets are all the same (e.g., COT Initiator of RB set #1 = COT Initiator of RB set #2 = .... = COT Initiator of RB set #M), the UE cannot perform the corresponding configured UL transmission. (ii) When the UL transmission performed by the UE corresponds to a Scheduled UL and the COT Initiator indicated by the DCI is X (where X is the UE or the BS), if it is not determined that the COT Initiator of all M RB sets is the same as the COT Initiator X indicated by the DCI (e.g., COT Initiator of RB set #1 = COT Initiator of RB set #2 =... = COT Initiator of RB set #M = X), the UE cannot perform the corresponding Scheduled UL transmission. As an example, in (i) / (ii), a process for UL transmission is performed in a state where the COT Initiator is not determined for the remaining RB sets (e.g., N M RB sets) (e.g., when signal detection / sensing for determining the COT Initiator is performed but not detected, or when the COT Initiator has not been determined for the remaining RB sets). Also, as an example, in (i) / (ii), if the COT Initiator of the M RB sets is not the same as the COT Initiator of the remaining other RB sets (e.g., NM RB sets), the UE performs an additional process to determine whether to drop the corresponding UL transmission.Alternatively, in (i) / (ii), even if the COT Initiator of the M RB sets is not identical to the COT Initiator of the remaining other RB sets (e.g., NM RB sets), the corresponding UL transmission is performed (exceptionally under certain conditions).

[0332] D. Or in other methods, for an RB set group consisting of multiple RB sets configured in the same cell (e.g., intra-carrier) or the same BWP (and / or a cell (RB set) group consisting of multiple cells (multiple RB sets configured in the corresponding cells) configured in the same frequency band (e.g., intra-band)):

[0333] When a guard band (e.g., intra-carrier) is configured between frequency-adjacent RB sets on a cell / BWP and a specific (allocated) RB set in the RB set group is configured / indicated as a specific type (e.g., configured or scheduled) UL transmission resource,

[0334] -If the determined / assumed / instructed COT Initiator A (e.g., UE-initiated COT or BS-initiated COT) for the corresponding assigned RB set matches, and the determined / assumed / instructed COT Initiator for the remaining RB sets (excluding the corresponding assigned RB set) matches COT Initiator A (if there is none or even if there is one), UL transmission is allowed / possible.

[0335] i. As an example, if the determined / assumed / instructed COT Initiator for the assigned RB set matches the UE-initiated COT, UL transmission is allowed / possible even if there is no specifically determined / assumed / instructed COT Initiator for the remaining RB set.

[0336] ii. Therefore, in this case, if the COT Initiator determined / assumed / indicated for the assigned RB set and the remaining RB set differs between the RB sets, UL transmission is not allowed / impossible (i.e., the UE operates to omit the corresponding UL transmission).

[0337] E. In another method, for an RB set group consisting of multiple RB sets configured in the same cell (e.g., intra-carrier) or the same BWP (and / or a cell (RB set) group consisting of multiple cells (multiple RB sets configured in the corresponding cells) configured in the same frequency band (e.g., intra-band)):

[0338] When a specific partial (allocated) RB set in an RB set group is configured / indicated as a specific type (e.g., configured or scheduled) UL transmission resource without a guard band (e.g., intra-carrier) being configured between adjacent RB sets in frequency on a cell / BWP,

[0339] - UL transmission is allowed / possible if the determined / assumed / instructed COT Initiator A (e.g., UE-initiated COT or BS-initiated COT) for the corresponding assigned RB set matches, and the determined / assumed / instructed COT Initiator (if any) for the remaining RB sets (excluding the corresponding assigned RB set) matches COT Initiator A. For convenience, this behavior is defined as "multi-RB set behavior 2."

[0340] i. As an example, if the determined / assumed / instructed COT Initiator for the assigned RB set matches the UE-initiated COT, UL transmission is allowed / possible even if there is no specifically determined / assumed / instructed COT Initiator for the remaining RB sets.

[0341] ii. Therefore, in this case, if the COT Initiator determined / assumed / indicated for the assigned RB set and the remaining RB set differs between the RB sets, UL transmission is not allowed / impossible (i.e., the UE operates to omit the corresponding UL transmission).

[0342] As a characteristic example, for an RB set group consisting of multiple RB sets configured in the same cell (e.g., intra-carrier) or the same BWP (and / or a cell (RB set) group consisting of multiple cells (multiple RB sets configured in the corresponding cells) configured in the same frequency band (e.g., intra-band)):

[0343] If a guard band (e.g., intra-carrier) is configured between frequency-adjacent RB sets in a cell / BWP, the UE operates based on multi-RB set behavior 1;

[0344] - If no guard band (e.g., intra-carrier) is configured between frequency-adjacent RB sets in a cell / BWP, the UE is specified to operate based on multi-RB set behavior 2.

[0345] F. As yet another (or additional) method, for an RB set group consisting of multiple RB sets configured on the same cell (e.g., intra-carrier) or the same BWP (and / or a cell (RB set) group consisting of multiple cells (multiple RB sets configured in the corresponding cells) configured on the same frequency band (e.g., intra-band)), a BS-initiated COT (or UL transmission based on the BS-initiated COT (e.g., scheduled)) is indicated (by a specific (e.g., UE-specific or UE group-common) DCI) for a specific FFP-g interval, or a DL signal corresponding thereto (transmitted based on the BS-initiated COT) is detected, or a specific (e.g., UE If there is at least one RB set (or an RB set including a specific DL signal / channel (e.g., an SSB (resources used for SS / PBCH transmission) on which broadcast transmission is performed and / or a specific CORESET (e.g., having the lowest ID / index) (set by MIB / SIB, etc.)) that is indicated as useful for DL ​​transmission / reception (by DCI (group-common or UE-specific)), the UE behavior is specified such that the UE does not perform UL transmission using any RB set (out of all RB sets) during the idle interval within the corresponding FFP-g (e.g., omit UL transmission (on all RB sets) that are configured / instructed to overlap in time with the corresponding idle interval).

[0346] i. In this case, not only for RB sets that operate (to perform UL transmission) based on BS-initiated COT, but also for RB sets that operate (to perform UL transmission) based on UE-initiated COT, the RB set operates so as not to perform UL transmission during the idle period within the FFP-g (for example, by omitting UL transmission that is set / instructed to overlap in time with the idle period on the RB set).

[0347] G. As yet another (or additional) method, when a specific (e.g., configured or scheduled) UL transmission (resource) is configured / instructed across multiple RB sets (channels) (within the same cell / carrier), and transmission / operation based on BS-initiated COT is determined / assumed for a specific FFP-g interval for some of the multiple RB sets, while transmission / operation based on UE-initiated COT is determined / assumed for a specific FFP-u interval for the remaining RB sets, the UE operates to omit UL transmission for resources configured / instructed to overlap in time with idle intervals corresponding to the FFP-g in all of the multiple RB sets, and for resources configured / instructed to overlap in time with idle intervals corresponding to the FFP-u (in all of the multiple RB sets).

[0348] i. In this case, the UE operates to drop UL transmission for resources configured / instructed to overlap with the idle period corresponding to FFP-g not only for RB sets determined / assumed for transmission / operation based on BS-initiated COT but also for RB sets determined / assumed for transmission / operation based on UE-initiated COT for multiple RB sets, and operates to drop UL transmission for resources configured / instructed to overlap with the idle period corresponding to FFP-u not only for RB sets determined / assumed for transmission / operation based on UE-initiated COT but also for RB sets determined / assumed for transmission / operation based on BS-initiated COT (for multiple RB sets). The term RB set is also referred to as a channel.

[0349] ii. Referring to Figure 21, FFP-g (BS FFP) and FFP-u (UE FFP) are each configured periodically in the time domain (e.g., higher layer signaling of semi-static channel access configuration(s)). For convenience, we will assume that three RB sets (or three channels) RB set #0, RB set #1, and RB set #2 are configured in the frequency domain, and a Configured UL is configured in the UE. i) Configured UL 1-1 is configured for two RB sets in the frequency domain and belongs to UE FFP #i and BS FFP #n in the time domain. However, in UE FFP #i, the UE initiates channel occupation for two RB sets #0 and #1, and Configured UL 1 does not overlap with the idle period of UE FFP #i occupied by the UE. Therefore, the UE transmits Configured UL 1 based on the UE initiated channel occupation in UE FFP #i. On the other hand, since Configured UL 1 is not set to RB Set #2, the base station occupies RB Set #2 in BS FFP #n, and even if Configured UL 1 overlaps with an idle period of BS FFP #n, Configured UL 1 is not dropped. ii) Configured UL 2-1 is set to three RB sets in the frequency domain and belongs to UE FFP #i and BS FFP #n+1 in the time domain, but the UE has initiated channel occupation for RB set #0 and RB set #1 in UE FFP #i, while the BS has initiated channel occupation for RB set #2 in BS FFP #n+1. In other words, in UE FFP #i+1, channel occupation of RB set #0 and RB set #1 is performed by the UE, and channel occupation of RB set #2 is performed by the base station. Since the three RB sets for Configured UL 2-1 do not have the same channel occupancy and Configured UL 2-1 overlaps with the idle period of UE FFP #i, the UE drops Configured UL 2-1.The Configured UL 2-1 is dropped as a whole (e.g., all of the multiple channels / RB sets configured as the UL transmission resources). iii) The Configured UL 2-2 is configured with three RB sets in the frequency domain and belongs to the UE FFP #i+2 and the BS FFP #n+1 in the time domain, but the UE has initiated channel occupation for RB set #0 in the UE FFP #i+2, while the BS has initiated channel occupation for RB set #2 in the BS FFP #n+1. Since the three RB sets for the Configured UL 2-2 do not have the same channel occupation and the Configured UL 2-2 overlaps with the idle period of the BS FFP #n+1, the UE drops the Configured UL 2-2. The Configured UL 2-2 is dropped as a whole (e.g., all of the multiple channels / RB sets configured as the UL transmission resources).

[0350] H. This is to prevent the impact of (UL-to-DL) interference on the BS-initiated COT / FFP due to UE-initiated COT transmission, and can prevent problems such as collision / interference between the BS-initiated COT and the UE-initiated COT in advance.

[0351] 2) Furthermore, in a situation where a carrier (i.e., a cell) configured with multiple RB sets and / or multiple cells (configured with one or more RB sets) are configured, the following operations can be considered in relation to determining the COT Initiator (e.g., UE-initiated COT or BS-initiated COT) from the perspective of the BS.

[0352] A. For an RB set group consisting of multiple RB sets configured on the same cell (e.g., intra-carrier) (and / or a cell (RB set) group consisting of multiple cells (multiple RB sets configured in the corresponding cells) configured on the same frequency band (e.g., intra-band)), if there is no RB set that is instructed (by a specific DCI) to be UE-initiated COT (or UL transmission (e.g., scheduled) based on UE-initiated COT) for a specific FFP-u interval, or in which a corresponding UL signal (transmitted based on UE-initiated COT) is detected, DL transmission based on BS-initiated COT is performed using RB sets (all or part) belonging to the RB set group in an FFP-g interval that overlaps in time with the corresponding FFP-u interval from the BS's perspective, or whose FFP start point is included in the corresponding FFP-u interval.

[0353] B. For an RB set group consisting of multiple RB sets configured on the same cell (e.g., intra-carrier) (and / or a cell (RB set) group consisting of multiple cells (multiple RB sets configured in the corresponding cells) configured on the same frequency band (e.g., intra-band)), if there is at least one RB set that is indicated (by a specific DCI) as UE-initiated COT (or UL transmission (e.g., scheduled) based on UE-initiated COT) for a specific FFP-u interval, or in which a corresponding UL signal (transmitted based on UE-initiated COT) is detected, no DL transmission based on BS-initiated COT is performed by any RB set belonging to the RB set group in an FFP-g interval that overlaps in time with the corresponding FFP-u interval from the BS's perspective, or whose FFP start point is included in the corresponding FFP-u interval.

[0354] 3) Furthermore, in a situation where a carrier (i.e., a cell) or BWP consisting of multiple RB sets is configured for a UE, the following operations can be considered in relation to determining the COT initiator (e.g., UE-initiated COT or BS-initiated COT) (from the UE perspective):

[0355] A. Operation 1: For an RB set group consisting of multiple RB sets configured in the same cell (e.g., intra-carrier) or the same BWP, when (at least) some (allocated) RB sets in the RB set group are configured / instructed to specific (e.g., configured or scheduled) UL transmission resources:

[0356] If the determined / assumed / indicated COT initiator A (e.g., UE-initiated COT or BS-initiated COT) for the relevant allocated RB set is identically matched (especially if the UL transmission is a scheduled UL transmission, it is detected / verified by the COT initiator A indicated by the DCI for all of the allocated set), and if the determined / assumed / indicated COT initiator for the remaining RB sets (excluding the relevant allocated RB set) matches the COT initiator A (if there is none or even if there is one), then UL transmission is allowed / possible.

[0357] i. As an example, if the determined / assumed / indicated COT initiator for some (allocated) RB sets is equal to the UE-initiated COT, UL transmission is allowed / possible even if there is no specifically determined / assumed / indicated COT initiator for the remaining RB sets.

[0358] ii. Therefore, in this case, if the COT initiator determined / assumed / indicated for some (allocated) RB sets and the remaining RB sets differs between the RB sets, UL transmission is not permitted / possible (the UE operates to omit the corresponding UL transmission).

[0359] B. Operation 2: For an RB set group consisting of multiple RB sets configured in the same cell (e.g., intra-carrier) or the same BWP, when (at least) some (allocated) RB sets in the RB set group are configured / instructed to specific (e.g., configured or scheduled) UL transmission resources:

[0360] If the COT initiator (e.g., UE-initiated COT or BS-initiated COT) determined / assumed / indicated for the allocated RB set matches equally (especially if the UL transmission is a scheduled UL transmission, if it is detected / verified by the COT initiator indicated by DCI for all of the allocated RB set), the UL transmission is allowed / possible regardless of whether the COT initiator matches the COT initiator determined / assumed / indicated for the remaining RB sets (excluding the allocated RB set).

[0361] i. As an example, if the determined / assumed / indicated COT initiator for some (allocated) RB sets matches the UE-initiated COT equally, UL transmission is allowed / possible even if the determined / assumed / indicated COT initiator for the remaining RB sets is BS-initiated COT.

[0362] ii. Therefore, in this case, if the COT initiator determined / assumed / instructed for a portion of the allocated RB sets differs between the RB sets, UL transmission is not permitted / possible (i.e., the UE operates to omit the corresponding UL transmission) (for convenience, this is referred to as "Operation 2-1"). For example, according to Operation 2-1, the portion of the allocated RB sets includes a first RB set and a second RB set, and UL transmission is not permitted / possible because the COT initiator of the first RB set differs from the COT initiator of the second RB set.

[0363] iii. In this case, if the COT initiator determined / assumed / instructed for some (allocated) RB sets differs between the RB sets, the UL transmission is performed based on the UE-initiated COT (this is referred to as "Operation 2-2" for convenience). For example, according to Operation 2-2, the some (allocated) RB sets include a first RB set and a second RB set, and based on the fact that the COT initiator of the first RB set differs from the COT initiator of the second RB set, only UE-initiated COT-based UL transmission is restricted / restricted to be allowed.

[0364] C. Operation 3: For an RB set group consisting of multiple RB sets configured in the same cell (e.g., intra-carrier) or the same BWP, when a specific allocated RB set in the RB set group is configured / instructed to a specific (e.g., configured or scheduled) UL transmission resource:

[0365] UL transmission is allowed / possible regardless of whether the determined / assumed / indicated COT initiator (e.g., UE-initiated COT or BS-initiated COT) for the corresponding allocated RB set matches or does not match.

[0366] i. As an example, UL transmission is allowed / possible even if the COT initiator determined / assumed / indicated for some (allocated) RB sets is UE-initiated COT for the first RB set and BS-initiated COT for the second RB set.

[0367] D.Note 1

[0368] i. If no (e.g., intra-carrier) guard band is configured between adjacent / consecutive RB sets on a cell / BWP, Operation 1 is applied, and if the corresponding intra-carrier guard band is configured, Operation 2 is applied.

[0369] ii. If no (e.g., intra-carrier) guard band is configured between adjacent / consecutive RB sets on a cell / BWP, Operation 1 is applied, and if the corresponding intra-carrier guard band is configured, Operation 3 is applied.

[0370] iii. If no (e.g., intra-carrier) guard band is configured between adjacent / consecutive RB sets on a cell / BWP, Operation 2 is applied, and if the corresponding intra-carrier guard band is configured, Operation 3 is applied.

[0371] E.Note 2

[0372] i. If the UL transmission is a scheduled UL transmission, Operation 2 applies, and if the UL transmission is a configured UL transmission, Operation 3 applies.

[0373] ii. (In Operation 2) If the UL transmission is a scheduled UL transmission and the determined / assumed COT initiator for some (allocated) RB sets differs between RB sets (either not all matching the COT initiator indicated by the DCI), the UE applies Operation 2-1 (in Operation 2).

[0374] iii. (In Operation 2) If the UL transmission is a configured UL transmission and the determined / assumed COT initiator for some (allocated) RB sets differs between the RB sets, the UE applies Operation 2-2 (in Operation 2).

[0375] Figure 22 shows an example of a UL signal transmission / reception process based on a decision of the COT Initiator. The embodiment of Figure 22 is an exemplary application scheme of the above proposal, and the scope of the present invention is not limited to Figure 22. Also, the above content can be referred to in order to understand the embodiment of Figure 22.

[0376] Referring to FIG. 22, a COT Initiator is determined for an RB set for UL transmission (K10). Determining the COT Initiator includes a process of detecting / sensing a signal. A COT Initiator is determined for each RB set. The UE determines the COT Initiator for each RB set on the FFP to which the RB set (at least allocated for UL transmission) belongs. In the case of configured UL transmission, depending on whether all COT Initiators of the (allocated) RB set are the same (t), the UE performs UL transmission (K25, performs the (necessary) channel access process for UL transmission) or drops the UL transmission (K20). On the other hand, in the case of scheduled UL transmission, the UE receives a DCI indicating the COT Initiator, and can determine whether all COT Initiators of the (allocated) RB set are the same as the COT Initiator indicated by the DCI (K15). If the COT Initiator is the same for all of the (allocated) RB sets, the UE can perform UL transmission (K25, perform the (necessary) channel access process for UL transmission). If it is determined that any of the (allocated) RB sets has a COT Initiator different from the COT initiator indicated by the DCI, the UE may drop the UL transmission under certain conditions or check certain conditions to determine whether to drop the UL transmission (K20). For example, as shown in FIG. 21, the certain condition relates to whether or not there is overlap with an idle period. If UL transmissions configured for multiple RB sets are not associated with the same channel occupancy and overlap with an idle period of the BS FFP and / or overlap with an idle period of the UE FFP, the UL transmission is dropped. As described above, for example, UL transmission is allowed / possible even if there is no specifically determined / assumed / instructed COT Initiator for the remaining RB sets (of the corresponding RB set group other than the allocated RB set).

[0377] [6] UE behavior for configured UL transmissions in FBE operating conditions

[0378] 1) If a specific configured UL transmission (resource) is started after the start of a specific FFP-u period (i.e., not aligned with the start of the corresponding FFP-u) and is configured to overlap with an idle period for the corresponding FFP-u (corresponding to the corresponding FFP-u period) (e.g., M80 in Figure 23), the following UE behavior may occur.

[0379] A. If the UE has already generated a UE-initiated COT for the FFP-u (e.g., performed UL transmission based on the UE-initiated COT at the start of the FFP-u) (e.g., M85 Yes in Figure 23, which is defined as "Case 1" for convenience), the UE operates to drop the configured UL transmission (e.g., M105 in Figure 23).

[0380] B. Otherwise, if the UE has not generated a UE-initiated COT for the FFP-u (e.g., has not performed UL transmission based on the UE-initiated COT at the start of the corresponding FFP-u) (e.g., M85 No in FIG. 23), and the configured UL transmission (resources) are set within a specific FFP-g interval (not overlapping with the idle interval corresponding to the corresponding FFP-g) (e.g., M90 Yes in FIG. 23), and the UE determines that a BS-initiated COT has already been generated for the corresponding FFP-g (e.g., has detected a DL signal based on the BS-initiated COT from the corresponding FFP-g) (e.g., M95 Yes in FIG. 23, which is defined as "Case 2" for convenience), then the UE operates to transmit the configured UL resources in the form of shared-COT based on the BS-initiated COT (e.g., M100 in FIG. 23).

[0381] C. Otherwise, for other cases that are neither Case 1 (e.g., M85 Yes in FIG. 23) nor Case 2 (e.g., M95 Yes in FIG. 23) (e.g., M90 No, M95 No in FIG. 23), the UE operates to drop the configured UL transmission (M105 in FIG. 23).

[0382] 2) When a specific configured UL transmission (multiple UL resources constituting it) is started at the start of a specific FFP-u interval (i.e., aligned with the start of the corresponding FFP-u) and (a specific portion of the multiple UL resources) is configured to overlap with an idle interval corresponding to the corresponding FFP-u, the following UE behavior is possible.

[0383] A. If a configured UL transmission (multiple UL resources constituting it) is initiated within a specific FFP-g interval and (all of the multiple UL resources) are configured so as not to overlap with the idle interval corresponding to the FFP-g, and the UE determines that a BS-initiated COT has already been generated for the FFP-g (e.g., if the UE detects a DL signal based on the BS-initiated COT from the FFP-g), the UE operates to transmit all of the configured UL resources in the form of shared-COT based on the BS-initiated COT (for convenience, this is defined as "Case A").

[0384] B. Otherwise, if the configured UL transmission (the multiple UL resources constituting it) is initiated within a specific FFP-g interval and (a specific portion of the multiple UL resources) is configured to overlap with the idle interval corresponding to the FFP-g, and the UE determines that a BS-initiated COT has already been generated for the FFP-g (e.g., if it detects a DL signal based on the BS-initiated COT from the FFP-g), the UE shall omit transmission for the specific portion of the configured UL resources that overlap with the idle interval, and operate to transmit only for the remaining resources (that do not overlap with the idle interval) in the form of shared-COT based on the BS-initiated COT (for convenience, this is defined as "Case B").

[0385] C. Otherwise, if neither Case A nor Case B applies, the UE omits transmission for certain resources among the configured UL resources that overlap with the idle interval corresponding to the FFP-u, and performs transmission based on the UE-initiated COT only for the remaining resources (which do not overlap with the idle interval) (by generating a UE-initiated COT for the FFP-u (e.g., by performing UL transmission based on the UE-initiated COT at the start of the FFP-u)).

[0386] Meanwhile, referring to Figure 24, (unlike the example of Figure 23), depending on the Configured UL and / or FFP (semi-static channel access) settings, even if the Configured UL occurs after the start of UE FFP #i, it may end before the idle interval of UE FFP #i (M40). If the UE has already started channel occupation in UE FFP #i (M45 Yes), the Configured UL is related to the UE-initiated channel occupation in UE FFP #i, and the Configured UL is performed based on the UE-initiated channel occupation (M70). If the UE has not yet started channel occupation in UE FFP #i (M45 No), and the Configured UL occurs in the BS FFP and ends before the idle interval of the BS FFP (M55 Yes), the UE determines whether the base station has started channel occupation in the BS FFP (M60). If it is not determined that the base station has already started channel occupation in the BS FFP (M60 No), the UE drops the Configured UL (M75). If it is determined that the base station has already started channel occupation in the BS FFP (M60 Yes), the Configured UL is related to channel occupation initiated by the BS (M65), and the UE transmits the Configured UL based on COT-sharing of the BS FFP. If the UE has not yet started channel occupation in UE FFP #i (M45 No), and the Configured UL occurs within the BS FFP and overlaps with an idle period of the BS FFP (M55 No), the UE drops the Configured UL (M75).

[0387] Meanwhile, depending on the Configured UL and / or semi-static channel access (FFP) settings, unlike the examples of Figures 23 and 24, the Configured UL may be generated from the start of the UE FFP. In this case, the operation of the terminal / base station follows Figure 25. Referring to Figure 25, the Configured UL is generated at the start of UE FFP #i and ends before the idle period of UE FFP #i (M05). If the Configured UL is generated in the BS FFP and ends before the idle period of the BS FFP (M10 Yes), the UE determines whether the base station has started channel occupation in the BS FFP (M15). If it is determined that the base station has already started channel occupation in the BS FFP (M15 Yes), the Configured UL is related to channel occupation initiated by the BS (M20), and the UE transmits the Configured UL based on COT-sharing of the BS FFP. If it cannot be determined that the base station has already started channel occupation within the BS FFP (M15 No), the UE determines that the Configured UL is related to channel occupation in UE FFP #i initiated by the UE, and if the UE has successfully started channel occupation in UE FFP #i, the Configured UL is transmitted (M30). If the Configured UL does not occur within the BS FFP, or if the Configured UL occurs within the BS FFP but overlaps with the idle period of the BS FFP (M10 No), and overlaps with the idle period of UE FFP #i, the Configured UL is dropped (M25, M35).If the Configured UL does not occur within the BS FFP, or if the Configured UL occurs within the BS FFP but overlaps with the idle interval of the BS FFP (M10 No), and (the Configured UL occurs from the start of UE FFP #i) ends before the idle interval of UE FFP #i, the UE determines that the Configured UL is related to channel occupation in UE FFP #i initiated by the UE, and if (under certain conditions) the UE successfully starts channel occupation in UE FFP #i, the configured UL transmission is performed (M25, M30). For example, the specific conditions for performing the configured UL transmission (M25, M30) include the terminal determining that the base station has not started channel occupation in the BS FFP that overlaps with the configured UL. If a configured UL transmission occurs within the BS FFP but overlaps with an idle period of the BS FFP, and the determination result in M10 is No, and the base station determines that channel occupation has already begun in the BS FFP, the UE drops the configured UL transmission that overlaps with the idle period of the BS FFP. On the other hand, if a configured UL transmission occurs within the BS FFP but overlaps with an idle period of the BS FFP, and the determination result in M10 is No, and the base station determines that channel occupation has not yet begun in the BS FFP, the UE performs the configured UL transmission based on UE-initiated channel occupation.

[0388] Figure 26 is a diagram illustrating a method for transmitting and receiving a Configured UL according to an embodiment. Referring to Figure 26, a UE receives configuration information for a Configured UL via higher layer signaling (2505). If the Configured UL occurs from the start of the UE FFP (2510 Yes), the UE operates as shown in Figure 25 (M05). If the Configured UL occurs after the start of the UE FFP (2510 No) and overlaps with the idle interval of the UE FFP (2515 No), the UE operates as shown in Figure 23 (M80). If the Configured UL occurs after the start of the UE FFP (2510 No) and ends before the idle interval of the UE FFP (2515 Yes), the UE operates as shown in Figure 24 (M40).

[0389] Figure 27 is a diagram illustrating the operation of a UE on a shared spectrum in a wireless communication system according to one embodiment. Figure 27 is an exemplary application scheme of the above proposal, and the scope of the present invention is not limited to Figure 27. The above content can also be referred to in order to understand the embodiment of Figure 27.

[0390] 27, a UE may receive, through higher layer signaling, configuration information for an uplink (UL) transmission configured on a shared spectrum (2705). As described above, the configured UL is a UL configured (semi-statically / semi-persistently) through RRC signaling, and includes, for example, but is not limited to, at least one of CG PUSCH, PRACH, PUCCH, and SRS.

[0391] The UE may perform a channel access procedure for the configured UL transmission on the shared spectrum (2710). The channel access procedure may comprise checking a plurality of conditions to determine whether to perform or drop the configured UL transmission, based on whether the configured UL transmission occurs after a beginning of a first period configured to support a UE-initiated channel occupancy and whether the configured UL transmission overlaps with an idle period included in the first period.The plurality of conditions may include: i) a first condition that the UE has not initiated channel occupancy in the first period; ii) a second condition that the Configured UL transmission occurs within a second period configured to support a base station (BS)-initiated channel occupancy and ends before an idle period of the second period; and iii) a third condition that a channel occupancy has already been initiated by a BS in the second period. All the plurality of conditions shall be satisfied for performing the Configured UL transmission.

[0392] The terminal drops the configured UL transmission based on the fact that any one of a plurality of conditions is not satisfied (e.g., M105 in FIG. 23). For example, the terminal drops the configured UL transmission based on the fact that channel occupation by the terminal has already started in the first interval (e.g., M85 Yes in FIG. 23). For example, the terminal drops the configured UL transmission based on the fact that the configured UL transmission occurs in the second interval but overlaps with an idle interval of the second interval (e.g., M90 No in FIG. 23). For example, the terminal can drop the configured UL transmission even if the configured UL transmission occurs in the second interval and ends before the idle interval of the second interval (e.g., M90 Yes in FIG. 23) without determining that channel occupation by the base station has already started in the second interval (e.g., M95 No in FIG. 23).

[0393] If all of the first, second, and third conditions are satisfied (e.g., M95 Yes in FIG. 23), the terminal performs configured UL transmission on a COT (channel occupancy time)-sharing basis in the second interval in which the base station starts channel occupation (e.g., M100 in FIG. 23).

[0394] The terminal can drop the configured UL transmission on all of the multiple channels in the interval that overlaps with at least one of the idle intervals, regardless of whether each channel is occupied by the terminal or the base station, based on the configured UL transmission being set on multiple channels in the frequency domain and overlapping with at least one of the idle intervals of the first interval or the idle interval of the second interval in the time domain, and all of the multiple channels not being associated with the same channel occupancy. For example, based on the fact that configured UL transmission is set on multiple channels in the frequency domain and overlaps with at least one of the idle sections of the first section or the idle section of the second section in the time domain, and the multiple channels include channels occupied by the terminal and channels occupied by the base station, the terminal can drop configured UL transmission on all of the multiple channels in the section overlapping with at least one of the idle sections, regardless of whether each channel is occupied by the terminal or the base station (e.g., Configured UL 2-1 and / or Configured UL 2-2 in FIG. 21 ).

[0395] The terminal may determine that the configured UL transmission is set on multiple channels in the frequency domain and overlaps with at least one of the idle intervals of the first interval or the idle intervals of the second interval in the time domain, and the multiple conditions may include a fourth condition that all of the multiple channels are associated with the same channel occupancy.

[0396] The first interval is periodically set via higher layer signaling for terminal-initiated channel occupancy, and the second interval is periodically set via higher layer signaling for base station-initiated channel occupancy.

[0397] Figure 28 is a diagram illustrating the operation of a base station on a shared spectrum in a wireless communication system according to one embodiment. Figure 28 is an exemplary application scheme of the above proposal, and the scope of the present invention is not limited to Figure 28. The above content can also be referred to in order to understand the embodiment of Figure 28.

[0398] 28, a base station transmits configuration information for configured UL (uplink) reception on a shared spectrum to a terminal (UE) via higher layer signaling 2805. As described above, the configured UL is a UL configured (semi-statically / semi-persistently) via RRC signaling, and includes, for example, at least one of CG PUSCH, PRACH, PUCCH, and SRS, but is not limited thereto.

[0399] The base station performs configured UL reception from the terminal on the shared spectrum (2810). Whether to perform configured UL reception is determined based on whether the configured UL reception occurs after the start of a first period configured to support UE-initiated channel occupancy and whether the configured UL reception overlaps with an idle period included in the first period. To perform configured UL reception, several conditions must be met: i) a first condition that the terminal has not started channel occupancy in the first period; ii) a second condition that the configured UL reception occurs within a second period configured to support UE-initiated channel occupancy and ends before the idle period of the second period; and iii) a third condition that channel occupancy by the base station has already started in the second period.

[0400] The configured UL reception is dropped when any one of a plurality of conditions is not satisfied (e.g., M105 in FIG. 23). For example, the configured UL reception is dropped when channel occupation by the terminal has already started in the first period (e.g., M85 Yes in FIG. 23). For example, the configured UL reception is dropped when the terminal's configured UL reception occurs in the second period but overlaps with an idle period of the second period (e.g., M90 No in FIG. 23). For example, even if the configured UL reception occurs in the second period and ends before the idle period of the second period (e.g., M90 Yes in FIG. 23), the configured UL reception is dropped without the base station starting channel occupation in the second period (e.g., M95 No in FIG. 23).

[0401] If all of the first, second, and third conditions are satisfied (e.g., M95 Yes in FIG. 23), configured UL reception is performed on a COT (channel occupancy time)-sharing basis in the second interval where the base station starts channel occupation (e.g., M100 in FIG. 23).

[0402] When configured UL reception is configured on multiple channels in the frequency domain and overlaps with at least one of the idle sections of the first section or the idle section of the second section in the time domain, and based on the fact that all of the multiple channels are not associated with the same channel occupancy, in the section overlapping with at least one of the idle sections, the configured UL reception is dropped on all of the multiple channels, regardless of whether each channel is occupied by the terminal or the base station. For example, when configured UL reception is configured on multiple channels in the frequency domain and overlaps with at least one of the idle sections of the first section or the idle section of the second section in the time domain, and based on the fact that the multiple channels include channels occupied by the terminal and channels occupied by the base station, in the section overlapping with at least one of the idle sections, the configured UL reception is dropped on all of the multiple channels, regardless of whether each channel is occupied by the terminal or the base station (e.g., Configured UL 2-1 and / or Configured UL 2-2 in FIG. 21 ).

[0403] configured The multiple conditions may include a fourth condition that all of the multiple channels are associated with the same channel occupancy, based on UL reception being configured on multiple channels in the frequency domain and overlapping with at least one of the idle intervals of the first interval or the idle intervals of the second interval in the time domain.

[0404] The first interval is periodically set via higher layer signaling for terminal-initiated channel occupancy, and the second interval is periodically set via higher layer signaling for base station-initiated channel occupancy.

[0405] FIG. 29 illustrates a communication system 1 to which the present invention can be applied.

[0406] Referring to FIG. 29, the communication system 1 includes wireless devices, base stations, and a network. Here, the wireless devices refer to devices that communicate using wireless connection technologies (e.g., 5G NR, LTE), and are also referred to as communication / wireless / 5G devices. The wireless devices include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an XR (eXtended Reality) device 100c, a handheld device 100d, a home appliance 100e, an IoT (Internet of Things) device 100f, and an AI server / device 400. For example, the vehicles include vehicles equipped with wireless communication capabilities, autonomous vehicles, vehicles capable of vehicle-to-vehicle communication, and the like. Here, the vehicles include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices include Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR) devices, and are embodied in the form of Head-Mounted Devices (HMDs), Head-Up Displays (HUDs) mounted on vehicles, TVs, smartphones, computers, wearable devices, home appliances, digital billboards, vehicles, robots, etc. Mobile devices include smartphones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., laptops, etc.), etc. Home appliances include TVs, refrigerators, washing machines, etc. IoT devices include sensors, smart meters, etc. For example, base stations and networks may also be embodied as wireless devices, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0407] The wireless devices 100a to 100f are connected to a network 300 via a base station 200. The wireless devices 100a to 100f are equipped with AI (Artificial Intelligence) technology, and are connected to an AI server 400 via the network 300. The network 300 is configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f can communicate with each other via the base station 200 / network 300, but can also communicate directly without going through the base station / network (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). IoT devices (e.g., sensors) can also communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0408] Wireless communication / connections 150a, 150b, and 150c are performed between the wireless devices 100a to 100f and the base stations 200, and between the base stations 200. Here, the wireless communication / connections are performed using various wireless connection technologies such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication), and communication between base stations 150c (e.g., relay, Integrated Access Backhaul (IAB)) (e.g., 5G NR). Through the wireless communication / connections 150a, 150b, and 150c, the wireless devices and the base stations, and the base stations, can transmit / receive wireless signals to / from each other. For example, the wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, according to various proposals of the present invention, any one of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes is performed.

[0409] FIG. 30 illustrates a wireless device to which the present invention can be applied.

[0410] 30, a first wireless device 100 and a second wireless device 200 transmit and receive wireless signals using various wireless access technologies (e.g., LTE, NR), where {first wireless device 100, second wireless device 200} corresponds to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in FIG.

[0411] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 is configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 102 processes information in the memory 104 to generate first information / signals and then transmits a wireless signal including the first information / signals via the transceiver 106. The processor 102 also receives a wireless signal including second information / signals via the transceiver 106 and then stores information obtained from signal processing of the second information / signals in the memory 104. The memory 104 is coupled to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code including instructions for performing some or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 is coupled to the processor 102 and transmits and / or receives wireless signals via one or more antennas 108. The transceiver 106 includes a transmitter and / or a receiver. The transceiver 106 may also be referred to as an RF (radio frequency) unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0412] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 is configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 202 processes information in the memory 204 to generate third information / signal, and then transmits a wireless signal including the third information / signal via the transceiver 206. The processor 202 also receives a wireless signal including a fourth information / signal via the transceiver 206, and then stores information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 is coupled to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code including instructions for performing some or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 is coupled to the processor 202 and transmits and / or receives wireless signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or a receiver. The transceiver 206 may also be referred to as an RF unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0413] The hardware elements of the wireless devices 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. The one or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. The one or more processors 102, 202 generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed herein and provide them to the one or more transceivers 106, 206. The one or more processors 102, 202 receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and derive the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein.

[0414] The one or more processors 102, 202 may also be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. For example, the one or more processors 102, 202 may include one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be implemented using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be included in the one or more processors 102, 202 or may be stored in one or more memories 104, 204 and executed by the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or flow charts disclosed in this specification may be embodied using firmware or software in the form of code, instructions and / or sets of instructions.

[0415] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0416] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., as referenced in the methods and / or flowcharts herein to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., as referenced in the descriptions, functions, procedures, suggestions, methods and / or flowcharts herein from one or more other devices. For example, one or more transceivers 106, 206 can be coupled to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 are coupled to one or more antennas 108, 208, and are configured to transmit and receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein via the one or more antennas 108, 208. In this specification, one or more antennas may refer to multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing by one or more processors 102, 202. The one or more transceivers 106, 206 convert the user data, control information, radio signals / channels, etc., processed by one or more processors 102, 202, from baseband signals to RF band signals. For this purpose, the one or more transceivers 106, 206 include (analog) oscillators and / or filters.

[0417] Figure 31 shows another example of a wireless device to which the present invention is applied. The wireless device may be implemented in various forms depending on the use case / service (see Figure 29).

[0418] 31, wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 30 and are composed of various elements, components, units / sections, and / or modules. For example, the wireless devices 100 and 200 include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit includes a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 includes one or more processors 102 and 202 and / or one or more memories 104 and 204 in FIG. 30. For example, the transceiver 114 includes one or more transceivers 106 and 206 and / or one or more antennas 108 and 208 in FIG. 30. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls the overall operation of the wireless device. For example, the control unit 120 controls the electrical / mechanical operations of the wireless device based on the programs / codes / instructions / information stored in the memory unit 130. The control unit 120 also transmits the information stored in the memory unit 130 to an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface, or stores information received from an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface in the memory unit 130.

[0419] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include any one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. Wireless devices may be embodied in the form of, but are not limited to, a robot (FIG. 29, 100a), a vehicle (FIG. 29, 100b-1, 100b-2), an XR device (FIG. 29, 100c), a mobile device (FIG. 29, 100d), a home appliance (FIG. 29, 100e), an IoT device (FIG. 29, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a FinTech device (or financial device), a security device, a climate / environment device, an AI server / device (FIG. 29, 400), a base station (FIG. 29, 200), a network node, etc. Wireless devices may be mobile or fixed depending on the use case / service.

[0420] In FIG. 31, the various elements, components, units / sections and / or modules within the wireless devices 100, 200 are all connected to each other by wired interfaces or at least some are connected wirelessly by a communication section 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first unit (e.g., 130, 140) are connected wirelessly via the communication unit 110. Furthermore, each element, component, unit / part and / or module in the wireless devices 100 and 200 further includes one or more elements. For example, the control unit 120 is configured with a set of one or more processors. For example, the control unit 120 is configured with a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 is configured with a RAM (Random Access Memory), a DRAM (Dynamic RAM), a ROM (Read Only Memory), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

[0421] 32 is a diagram illustrating an example of a vehicle or an autonomous vehicle to which the present invention is applied. The vehicle or the autonomous vehicle may be embodied as a mobile robot, a car, a train, an aerial vehicle (AV), a ship, etc.

[0422] 32, a vehicle or autonomous vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 is configured as part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 in FIG. 31, respectively.

[0423] The communication unit 110 transmits and receives signals (e.g., data, control signals, etc.) to and from external devices such as other vehicles, base stations (e.g., base stations, roadside units, etc.), and servers. The control unit 120 controls elements of the vehicle or autonomous vehicle 100 to perform various operations. The control unit 120 includes an ECU (Electronic Control Unit). The driving unit 140a causes the vehicle or autonomous vehicle 100 to move on the ground. The driving unit 140a includes an engine, a motor, a powertrain, wheels, brakes, a steering device, etc. The power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and includes wired / wireless charging circuits, a battery, etc. The sensor unit 140c can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit 140c includes an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / reverse sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit 140d implements technology for maintaining a lane while driving, technology for automatically adjusting speed such as adaptive cruise control, technology for automatically driving along a predetermined route, technology for automatically setting a route and driving when a destination is set, etc.

[0424] For example, the communication unit 110 receives map data, traffic information data, etc. from an external server. The autonomous driving unit 140d generates an autonomous driving route and a driving plan based on the obtained data. The control unit 120 controls the driving unit 140a (e.g., adjusting speed / direction) so that the vehicle or autonomous vehicle 100 moves along the autonomous driving route according to the driving plan. The communication unit 110 aperiodically obtains the latest traffic information data from an external server during autonomous driving and also obtains surrounding traffic information data from surrounding vehicles. In addition, the sensor unit 140c obtains vehicle status and surrounding environment information during autonomous driving. The autonomous driving unit 140d updates the autonomous driving route and driving plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, autonomous driving route, driving plan, etc. to an external server. The external server can predict traffic information data using AI technology based on information collected from the vehicle or autonomous vehicle and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0425] FIG. 33 is a diagram illustrating the DRX (Discontinuous Reception) operation of a terminal according to one embodiment of the present invention.

[0426] A terminal can perform DRX operation while executing the procedures and / or methods described / proposed above. A terminal configured for DRX can reduce power consumption by discontinuously receiving DL signals. DRX is performed in the RRC (Radio Resource Control)_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. DRX in the RRC_IDLE state and RRC_INACTIVE state is used to discontinuously receive paging signals. DRX performed in the RRC_CONNECTED state will be described below (RRC_CONNECTED DRX).

[0427] Referring to FIG. 33, a DRX cycle consists of On Duration and Opportunity for DRX. The DRX cycle defines a time interval during which On Duration is periodically repeated. On Duration indicates a time period during which the UE monitors to receive the PDCCH. When DRX is configured, the UE monitors the PDCCH during On Duration. If a PDCCH is successfully detected during PDCCH monitoring, the UE operates an inactivity timer and remains awake. On the other hand, if a PDCCH is not successfully detected during PDCCH monitoring, the UE enters a sleep state after the On Duration expires. Therefore, when DRX is configured, PDCCH monitoring / reception is performed discontinuously in the time domain when the above-described / proposed procedures and / or methods are performed. For example, when DRX is configured, in the present invention, PDCCH reception opportunities (e.g., slots having a PDCCH search space) are configured discontinuously according to the DRX configuration. On the other hand, if DRX is not configured, when the above-described / proposed procedures and / or methods are performed, PDCCH monitoring / reception is performed continuously in the time domain. For example, if DRX is not configured, in the present invention, PDCCH reception opportunities (e.g., slots having PDCCH search spaces) are configured continuously. On the other hand, PDCCH monitoring may be restricted in the time interval configured as the measurement gap, regardless of whether DRX is configured.

[0428] Table 9 shows the process of the UE related to DRX (RRC_CONNECTED state). Referring to Table 9, DRX configuration information is received via higher layer (e.g., RRC) signaling, and DRX ON / OFF is controlled by a DRX command of the MAC layer. When DRX is configured, the UE can perform PDCCH monitoring discontinuously when performing the procedures and / or methods described / proposed in the present invention.

[0429] [Table 9]

[0430] Here, MAC-CellGroupConfig includes configuration information required to set MAC (Medium Access Control) parameters for a cell group. MAC-CellGroupConfig may also include configuration information related to DRX. For example, MAC-CellGroupConfig includes the following information in the definition of DRX:

[0431] - Value of drx-OnDurationTimer: Defines the length of the start period of the DRX cycle

[0432] Value of drx-InactivityTimer: defines the length of the time interval in which the terminal is in an awake state after a PDCCH opportunity in which a PDCCH indicating initial UL or DL ​​data is detected

[0433] - Value of drx-HARQ-RTT-TimerDL: Defines the maximum time interval between when a DL initial transmission is received and when a DL retransmission is received

[0434] - Value of drx-HARQ-RTT-TimerDL: Defines the maximum time interval between when a grant for UL initial transmission is received and when a grant for UL retransmission is received.

[0435] -drx-LongCycleStartOffset: Defines the length and start of a DRX cycle

[0436] -drx-ShortCycle(optional): Defines the time length of a short DRX cycle

[0437] Here, if any one of the drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is running, the terminal remains awake and performs PDCCH monitoring at every PDCCH opportunity.

[0438] The above-described embodiments are combinations of the elements and features of the present invention in a predetermined form. Each element or feature should be considered optional unless otherwise explicitly stated. Each element or feature may be implemented without being combined with other elements or features. It is also possible to combine some elements and / or features to form an embodiment of the present invention. The order of operations described in the embodiments of the present invention may be changed. Some elements or features of any embodiment may be included in other embodiments, or may be replaced with corresponding elements or features of other embodiments. It is obvious that claims that are not explicitly cited in the claims may be combined to form an embodiment, or may be included as new claims by amendment after filing.

[0439] It is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the characteristics of the present invention. Therefore, the above detailed description should not be construed as limiting in all respects, but should be considered as illustrative. The scope of the present invention should be determined by reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention. [Industrial Applicability]

[0440] The present invention can be used in a terminal, a base station or other equipment of a wireless mobile communication system.

Claims

1. A method for a terminal (UE) to transmit a signal in a wireless communication system, comprising: receiving configuration information for a configured UL (uplink) transmission on a shared spectrum via higher layer signaling; performing a channel access procedure for the configured UL transmission; The channel connection process includes: checking a plurality of conditions for determining whether to perform or drop the configured UL transmission based on the configured UL transmission occurring after a start of a first period configured to support UE-initiated channel occupancy and overlapping an idle period included in the first period, The plurality of conditions include: i) a first condition that the terminal has not started channel occupancy in the first interval; ii) a second condition that the configured UL transmission occurs within a second interval configured to support base station (BS)-initiated channel occupancy and ends before an idle interval of the second interval; and iii) a third condition that channel occupancy by the base station has already started in the second interval. The method, wherein all of the conditions must be satisfied in order for the configured UL transmission to occur.

2. The method of claim 1 , wherein the terminal drops the configured UL transmission based on any one of the plurality of conditions not being met.

3. The method of claim 1 , wherein the terminal drops the configured UL transmission on the basis that channel occupation by the terminal has already started in the first time interval.

4. The method of claim 1 , wherein the terminal drops the configured UL transmission based on the configured UL transmission occurring within the second interval but overlapping with an idle interval of the second interval.

5. 2. The method of claim 1, wherein the terminal drops the configured UL transmission even if the configured UL transmission occurs within the second interval and ends before an idle interval of the second interval, without determining that channel occupation by the base station has already started in the second interval.

6. 2. The method of claim 1, wherein the terminal performs the configured UL transmission on a channel occupancy time (COT)-sharing basis in the second interval in which channel occupation of the base station begins based on the first condition, the second condition, and the third condition being all satisfied.

7. The terminal determines whether the configured UL transmission is configured on a plurality of channels in a frequency domain, overlaps with at least one of an idle section of the first section or an idle section of the second section in a time domain, and the plurality of channels include a channel occupied by the terminal and a channel occupied by the base station.

2. The method of claim 1, further comprising: dropping the configured UL transmission on all of the plurality of channels in an interval overlapping with at least one of the idle intervals, regardless of whether each channel is occupied by the terminal or the base station.

8. The terminal determines, based on the fact that the configured UL transmission is configured on a plurality of channels in a frequency domain and overlaps with at least one of an idle period of the first section or an idle period of the second section in a time domain, and all of the plurality of channels are not associated with a same channel occupancy, 2. The method of claim 1, further comprising: dropping the configured UL transmission on all of the plurality of channels in an interval overlapping with at least one of the idle intervals, regardless of whether each channel is occupied by the terminal or the base station.

9. The terminal determines whether the configured UL transmission is configured on a plurality of channels in a frequency domain and overlaps with at least one of an idle period of the first section or an idle period of the second section in a time domain. The method of claim 1 , wherein the plurality of conditions includes a fourth condition that all of the plurality of channels are associated with the same channel occupancy.

10. The first period is periodically set via higher layer signaling for the terminal-initiated channel occupancy, The method of claim 1, wherein the second interval is periodically set via higher layer signaling for the base station-initiated channel occupancy.

11. A computer-readable recording medium having a program recorded thereon for carrying out the method according to claim 1.

12. A terminal for transmitting a signal in a wireless communication system, A transceiver; a processor for receiving configuration information for a configured UL (uplink) transmission on a shared spectrum through higher layer signaling by controlling the transceiver, and performing a channel connection process for the configured UL transmission; The channel connection process includes: checking a plurality of conditions for determining whether to perform or drop the configured UL transmission based on the configured UL transmission occurring after a start of a first period configured to support UE-initiated channel occupancy and overlapping an idle period included in the first period, The plurality of conditions include: i) a first condition that the terminal has not started channel occupancy in the first interval; ii) a second condition that the configured UL transmission occurs within a second interval configured to support base station (BS)-initiated channel occupancy and ends before an idle interval of the second interval; and iii) a third condition that channel occupancy by the base station has already started in the second interval. In order to perform the configured UL transmission, all of the multiple conditions must be satisfied.

13. An apparatus for controlling a terminal (UE) in a wireless communication system, A memory for storing instruction words; a processor that executes the instructions to perform an operation; The operation of the processor includes: receiving configuration information for a configured UL (uplink) transmission on a shared spectrum via higher layer signaling; performing a channel access procedure for the configured UL transmission; The channel connection process includes: checking a plurality of conditions for determining whether to perform or drop the configured UL transmission based on the configured UL transmission occurring after a start of a first period configured to support UE-initiated channel occupancy and overlapping an idle period included in the first period, The plurality of conditions include: i) a first condition that the terminal has not started channel occupancy in the first interval; ii) a second condition that the configured UL transmission occurs within a second interval configured to support base station (BS)-initiated channel occupancy and ends before an idle interval of the second interval; and iii) a third condition that channel occupancy by the base station has already started in the second interval. In order to perform the configured UL transmission, all of the multiple conditions must be satisfied.

14. A method for a base station (BS) receiving a signal in a wireless communication system, comprising: transmitting, via higher layer signaling, configuration information for configured UL (uplink) reception on a shared spectrum to a terminal (UE); performing the configured UL reception from the terminal; the configured UL reception occurs after a start of a first period configured to support UE-initiated channel occupancy, and whether or not to perform the configured UL reception is determined based on whether the configured UL reception overlaps with an idle period included in the first period; A method in which, in order to perform the configured UL reception, a number of conditions must all be satisfied, including: i) a first condition that the terminal has not started channel occupancy in the first interval; ii) a second condition that the configured UL reception occurs within a second interval configured to support base station-initiated channel occupancy and ends before an idle interval of the second interval; and iii) a third condition that channel occupancy by the base station has already started in the second interval.

15. 1. A base station for receiving a signal in a wireless communication system, comprising: A transceiver; a processor for controlling the transceiver to transmit configuration information for configured UL (uplink) reception on a shared spectrum to a terminal (UE) via higher layer signaling and performing the configured UL reception from the terminal; the configured UL reception occurs after a start of a first period configured to support UE-initiated channel occupancy, and whether or not to perform the configured UL reception is determined based on whether the configured UL reception overlaps with an idle period included in the first period; A base station in which, in order to perform the configured UL reception, multiple conditions must all be satisfied, including: i) a first condition that the terminal has not started channel occupancy in the first interval; ii) a second condition that the configured UL reception occurs within a second interval configured to support base station-initiated channel occupancy and ends before an idle interval of the second interval; and iii) a third condition that channel occupancy by the base station has already started in the second interval.