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

Abstract

A method and apparatus for transmitting and receiving a signal in a wireless communication system are provided. According to an embodiment of the disclosure, a user equipment (UE) can receive configuration information for channel access based on a UE-initiated channel occupancy on a shared spectrum and determine whether an uplink (UL) transmission associated with the UE-initiated channel occupancy is allowed during a first period based on the configuration information. Based on a resource for the UL transmission associated with the UE-initiated channel occupancy in the first period being related to a contention-based random access procedure, the UE can determine that the UL transmission associated with the UE-initiated channel occupancy is not allowed in the first period.

Description

[0001] This application claims the benefit of Korean Patent Application No. 10-2022-0003516, filed on January 10, 2022, which is hereby incorporated by reference as if fully set forth herein. Technical Field

[0002] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting or receiving downlink / uplink radio signals in the wireless communication system. Background Art

[0003] In general, wireless communication systems are developing to provide communication services such as audio communication services and data communication services with various coverage areas. Wireless communication is a multiple-access system that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). For example, a multiple-access system may be any of a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single-carrier frequency division multiple access (SC-FDMA) system. Summary of the Invention

[0004] Accordingly, the present disclosure is directed to a method and apparatus for transmitting and receiving signals in a wireless communication system that substantially obviate one or more problems due to limitations and disadvantages of the related art.

[0005] An object of the present disclosure is to provide a method and apparatus for efficiently performing a wireless signal transmission / reception process.

[0006] Those skilled in the art will understand that the purposes that can be achieved using the present disclosure are not limited to those specifically described above, and the above and other purposes that can be achieved by the present disclosure will be more clearly understood from the following detailed description.

[0007] To achieve these objectives and other advantages and in accordance with the purposes of the present disclosure, as embodied and broadly described herein, a method for performing a channel access procedure on a shared spectrum by a user equipment (UE) in a wireless communication system is provided. The method may include: receiving configuration information for channel access based on UE-initiated channel occupancy; determining whether uplink (UL) transmission associated with the UE-initiated channel occupancy is allowed during a first time period based on the configuration information; and accessing the channel based on a result of the determination. Based on the fact that resources used for UL transmission associated with the UE-initiated channel occupancy in the first time period are related to a random access procedure, and the random access procedure is a contention-based random access procedure, the UE may determine that UL transmission associated with the UE-initiated channel occupancy is not allowed during the first time period.

[0008] Based on the random access procedure being a contention-based random access procedure, the UE may determine that UL transmission associated with UE-initiated channel occupancy is not allowed during the random access procedure.

[0009] Based on determining that UL transmission associated with UE-initiated channel occupancy is not allowed, the UE performs UL transmission by accessing the channel in a second period starting with base station-initiated (BS-initiated) channel occupancy shared based on channel occupancy time (COT).

[0010] While the UE is in a radio resource control (RRC) inactive mode or an RRC idle mode, UL transmissions associated with UE-initiated channel occupation may not be allowed.

[0011] Based on the UE being in RRC connected mode and the random access procedure not being a contention-based random access procedure, the UE may determine that UL transmission associated with the UE-initiated channel occupation is allowed in the first time period based on the configuration information.

[0012] Based on the UE being in RRC connected mode, but resources used for UL transmission associated with UE-initiated channel occupation in the first period are related to a contention-based random access procedure, the UE may determine that UL transmission associated with UE-initiated channel occupation is not allowed in the first period.

[0013] The UL transmission may include UL transmission related to a random access procedure.

[0014] The UE may determine that UL transmissions associated with UE-initiated channel occupancy are not allowed for the following: physical random access channel (PRACH) resources, physical uplink shared channel (PUSCH) resources for message 3 (Msg3), message A (MsgA) resources including a PRACH preamble in a 2-step random access, or physical uplink control channel (PUCCH) resources carrying a hybrid automatic repeat request acknowledgement (HARQ-ACK) for message B (MsgB) as a response to MsgA, which is associated with a contention-based random access procedure.

[0015] The random access procedure can be used for timing advance (TA) adjustment, scheduling request (SR) or beam failure report (BFR) in the radio resource control (RRC) connected state.

[0016] In another aspect of the present disclosure, a computer-readable storage medium is provided, on which a program for executing the above method is stored.

[0017] In another aspect of the present disclosure, a UE configured to perform the above-mentioned channel access procedure is provided.

[0018] In another aspect of the present disclosure, a device configured to control a UE that performs the above-mentioned channel access procedure is provided.

[0019] In another aspect of the present disclosure, a method for a base station (BS) to receive a signal from a UE on a shared spectrum in a wireless communication system is provided. The method may include: transmitting configuration information for channel access based on UE-initiated channel occupancy; determining whether to allow UL transmission associated with the UE-initiated channel occupancy during a first time period based on the configuration information; and receiving a UL signal based on a result of the determination. Based on the fact that resources used for UL transmission associated with the UE-initiated channel occupancy in the first time period are related to a random access procedure, and the random access procedure is a contention-based random access procedure, the BS may determine that UL transmission associated with the UE-initiated channel occupancy is not allowed during the first time period.

[0020] Based on determining that UL transmission associated with UE-initiated channel occupancy is not allowed in the first time period, a UL signal may be received in a second time period starting with BS-initiated channel occupancy based on COT sharing.

[0021] In another aspect of the present disclosure, a BS configured to perform the above method is provided.

[0022] It is to be understood that both the foregoing general description and the following detailed description of the present disclosure are exemplary and explanatory and are intended to provide further explanation of the disclosure as claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings, which are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this application, illustrate embodiments of the present disclosure and together with the description serve to explain the principles of the present disclosure. In the drawings:

[0024] Figure 1 Illustrate physical channels used in a 3rd Generation Partnership Project (3GPP) system as an exemplary wireless communication system and a general signal transmission method using the physical channels;

[0025] Figure 2 Figure 1 shows the radio frame structure;

[0026] Figure 3 A resource grid illustrating time slots is shown;

[0027] Figure 4 illustrates an exemplary mapping of physical channels in time slots;

[0028] Figure 5 An exemplary ACK / NACK transmission process is illustrated;

[0029] Figure 6 illustrates an exemplary physical uplink shared channel (PUSCH) transmission process;

[0030] Figure 7 An example of multiplexing control information in a PUSCH is shown;

[0031] Figure 8 An exemplary wireless communication system supporting unlicensed bands is illustrated;

[0032] Figure 9 An exemplary method of occupying resources in an unlicensed band is illustrated;

[0033] Figure 10 Illustrate an exemplary frame-based equipment (FBE) based channel access;

[0034] Figure 11 FIGURES AN illustrative example of channel access based on load-based equipment (LBE);

[0035] Figure 12 is a flow chart illustrating a Type 1 Channel Access Procedure (CAP) of a base station (BS) for downlink (DL) signal transmission (e.g., an example of LBE-based channel access);

[0036] Figure 13 is a flow chart illustrating a Type 1 CAP (e.g., an example of LBE-based channel access) for user equipment (UE) for uplink (UL) signal transmission;

[0037] Figure 14 illustrates an exemplary plurality of LBT sub-bands (LBT-SBs) included in a frequency band (e.g., a bandwidth part (BWP)) in a shared spectrum;

[0038] Figure 15 and Figure 16 illustrates a fixed frame period (FFP) according to an embodiment of the present disclosure;

[0039] Figures 17 to 25 is a diagram for explaining a UL signal transmission / reception method according to an embodiment of the present disclosure;

[0040] Figures 26 to 29 illustrates a communication system 1 and a wireless device suitable for use with the present disclosure; and

[0041] Figure 30 The diagram illustrates a discontinuous reception (DRX) operation applicable to the present disclosure. DETAILED DESCRIPTION

[0042] Reference will now be made in detail to the preferred embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or like parts.

[0043] Embodiments of the present disclosure are applicable to various wireless access technologies 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 as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (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.

[0044] As more and more communication devices require greater communication capacity, enhanced mobile broadband communication relative to traditional radio access technology (RAT) is needed. In addition, large-scale machine type communication (MTC), which can provide various services anytime and anywhere by connecting multiple devices and objects, is another important issue to be considered in the next generation of communications. Discussions are also underway to design communication systems that take into account services / UEs that are sensitive to reliability and latency. Therefore, discussions are underway to introduce new radio access technologies that take into account enhanced mobile broadband communication (eMBB), massive MTC, and ultra-reliable low-latency communication (URLLC). In this disclosure, for simplicity, this technology will be referred to as NR (new radio or new RAT).

[0045] For the sake of brevity, 3GPP NR is mainly described, but the technical concept of the present disclosure is not limited thereto.

[0046] In this disclosure, the term "set" / setting can be replaced with "configure" / configuration, and the two can be used interchangeably. Furthermore, conditional expressions (e.g., "if," "in this case," or "when...") can be replaced with "based on" or "under the circumstances / states." Furthermore, the operation or software / hardware (SW / HW) configuration of a user equipment (UE) / base station (BS) can be derived / understood based on the satisfaction of the corresponding condition. When a receiving (or transmitting) side process can be derived / understood from a transmitting (or receiving) side process in signal transmission / reception between a wireless communication device (e.g., a BS and a UE), its description may be omitted. For example, signal determination / generation / encoding / transmission on the transmitting side can be understood as signal monitoring, reception, decoding, and determination on the receiving side. Furthermore, when it is said that a UE performs (or does not perform) a specific operation, this can also be interpreted as the BS expecting / assuming (or not expecting / assuming) that the UE performs the specific operation. When it is said that a BS performs (or does not perform) a specific operation, this can also be interpreted as the UE expecting / assuming (or not expecting / assuming) that the BS performs the specific operation. In the following description, for the sake of convenience, sections, embodiments, examples, options, methods, schemes, etc. are distinguished from each other and marked with indexes, which does not mean that each of them necessarily constitutes an independent invention or that each of them can only be implemented alone. Unless clearly contradicted, it can be inferred / understood that at least some of the sections, embodiments, examples, options, methods, schemes, etc. can be implemented in combination or can be omitted.

[0047] In a wireless communication system, a user equipment (UE) receives information from a base station (BS) via a downlink (DL) and transmits information to the BS via an uplink (UL). The information transmitted and received by the BS and the UE includes data and various control information, and includes various physical channels depending on the type and purpose of the information transmitted and received by the UE and the BS.

[0048] Figure 1 This diagram illustrates physical channels used in a 3GPP NR system and a general signal transmission method using the same.

[0049] When the UE is powered on again from a power-off state or enters a new cell, in step S101, the UE performs an initial cell search process (e.g., establishing synchronization with the BS). To this end, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE establishes synchronization with the BS based on the PSS / SSS and obtains information such as a cell identity (ID). The UE can obtain broadcast information in the cell based on the PBCH. During the initial cell search, the UE can receive a DL reference signal (RS) to monitor the DL channel status.

[0050] After the initial cell search, the UE may acquire more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information of the PDCCH in step S102.

[0051] In steps S103 to S106, the UE may perform a random access procedure to access the BS. For random access, the UE may transmit a preamble to the BS on a physical random access channel (PRACH) (S103) and receive a response message to the preamble on a PDCCH and a PDSCH corresponding to the PDCCH (S104). In the case of contention-based random access, the UE may further perform a contention resolution procedure by transmitting a PRACH (S105) and receiving a PDCCH and a PDSCH corresponding to the PDCCH (S106).

[0052] After the aforementioned process, the UE may receive PDCCH / PDSCH (S107) and send a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108) as a general downlink / uplink signal transmission process. The control information sent from the UE to the BS is called uplink control information (UCI). UCI includes hybrid automatic repeat and request acknowledgement / negative confirmation (HARQ-ACK / NACK), scheduling request (SR), channel state information (CSI), etc. CSI includes channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), etc. Although UCI is usually sent on PUCCH, when control information and service data need to be sent simultaneously, UCI can be sent on PUSCH. In addition, UCI can be sent aperiodically via PUSCH according to the request / command of the network.

[0053] The purpose of the random access procedure (RACH procedure) is not limited to initial network access (e.g., S103 to S106). That is, the random access procedure can be used for various purposes. For example, the random access procedure can be used for at least one of the RRC connection re-establishment procedure, handover, UE-triggered UL data transmission, transition from RRC_INACTIVE, SCell time alignment, system information request, beam failure recovery, or UL resource request. However, the random access procedure is not limited to this. The UE can acquire UL synchronization and / or UL transmission resources from the random access procedure. The random access procedure can be divided into: 1) contention-based random access procedure and 2) contention-free random access procedure.

[0054] 1) Contention-based random access (CBRA) is divided into 4-step CBRA and 2-step CBRA. 4-step CBRA may be referred to as type 1, and 2-step CBRA may be referred to as type 2.

[0055] First, the four-step CBRA will be described. The UE may transmit Message 1 (Msg1) including a preamble associated with a specific sequence via the PRACH and receive Message 2 (Msg2) including a Random Access Response (RAR) via the PDCCH and its associated PDSCH. The UE may transmit Message 3 (Msg3) via the PUSCH based on scheduling information in the RAR. The UE may receive Message 4 (Msg4) including contention resolution information used for the contention resolution process from the base station.

[0056] Next, we will describe the 2-step CBRA process. The transmission of Msg1 and Msg3 in the 4-step CBRA process can be replaced by the transmission of a single message: Message A (MsgA) in the 2-step CBRA process, which includes both the PRACH and PUSCH. Specifically, MsgA can include the PRACH preamble in Msg1 and the data in Msg3. Furthermore, the transmission of Msg2 and Msg4 in the 4-step CBRA process can be replaced by the transmission of a single message: Message B (MsgB) in the 2-step CBRA process, which includes the BS's RAR and contention resolution information. Specifically, MsgB can include the RAR in Msg2 and the contention resolution information in Msg4.

[0057] 2) When the UE is handed over to another cell or another BS or when requested by a command from the BS, a contention-free random access (CFRA) can be performed. The basic steps of CFRA are similar to those of CBRA. However, in CFRA, the BS can explicitly indicate to the UE the dedicated random access preamble to be used by the UE, which is different from CBRA in which the UE autonomously selects the preamble to be used from multiple random access preambles. Information about the dedicated random access preamble can be included in an RRC message (e.g., a handover command) or provided to the UE via a PDCCH command. When the random access procedure is initiated, the UE sends a dedicated random access preamble to the BS. When the UE receives an RAR from the BS, the random access procedure can be completed.

[0058] CBRA may be referred to as CB-RACH, and CFRA may be referred to as CF-RACH.

[0059] Figure 2Figure 1 shows the radio frame structure. In NR, uplink and downlink transmissions are configured in frames. Each radio frame has a length of 10ms and is divided into two 5ms half-frames (HF). Each half-frame is divided into five 1ms subframes (SF). A subframe is divided into one or more time slots, and the number of time slots in a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 orthogonal frequency division multiplexing (OFDM) symbols. When a normal CP is used, each time slot includes 14 OFDM symbols. When an extended CP is used, each time slot includes 12 OFDM symbols.

[0060] Table 1 exemplarily shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when a normal CP is used.

[0061] [Table 1]

[0062] <![CDATA[SCS(15*2 u )]]> <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 15KHz (u=0) 14 10 1 30KHz (u=1) 14 20 2 60KHz (u=2) 14 40 4 120KHz (u=3) 14 80 8 240KHz (u=4) 14 160 16

[0063] *N slot symb : The number of symbols in a time slot

[0064] *N frame,u slot : Number of time slots in a frame

[0065] *N subframe,u slot : Number of time slots in a subframe

[0066] Table 2 shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS when the extended CP is used.

[0067] [Table 2]

[0068] <![CDATA[SCS(15*2 u )]]> <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 60KHz (u=2) 12 40 4

[0069] The structure of the frame is only an example. The number of subframes, the number of time slots, and the number of symbols in a frame may vary.

[0070] In an NR system, OFDM parameter sets (e.g., SCSs) may be configured differently for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., SF, time slot, or TTI) consisting of the same number of symbols (referred to as a time unit (TU) for simplicity) may be configured differently between the aggregated cells. Symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform-Spread-OFDM (DFT-s-OFDM) symbols).

[0071] Figure 3A resource grid showing a time slot. A time slot includes multiple symbols in the time domain. For example, when a normal CP is used, a time slot includes 14 symbols. However, when an extended CP is used, a time slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as a plurality of consecutive subcarriers in the frequency domain (e.g., 12 consecutive subcarriers). A bandwidth part (BWP) can be defined as a plurality of consecutive physical RBs (PRBs) in the frequency domain and corresponds to a single parameter set (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., five) BWPs. Data communication can be performed via enabled BWPs, and only one BWP can be enabled for a UE. In the resource grid, each element is called a resource element (RE), and one complex symbol can be mapped to each RE.

[0072] Figure 4 Figure 1 illustrates an exemplary mapping of physical channels in a time slot. The PDCCH can be sent in the DL control region, and the PDSCH can be sent in the DL data region. The PUCCH can be sent in the UL control region, and the PUSCH can be sent in the UL data region. The guard period (GP) provides a time gap for switching from transmission mode to reception mode or from reception mode to transmission mode at the BS and UE. Some symbols in a subframe during DL to UL switching can be configured as GPs.

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

[0074] PDCCH delivers DCI. For example, PDCCH (i.e., DCI) can carry information about the transport format and resource allocation of the DL shared channel (DL-SCH), resource allocation information of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about DL-SCH, information about resource allocation of higher-layer control messages (such as RAR sent on PDSCH), transmit power control commands, information about activation / release of configured scheduling, etc. DCI includes a cyclic redundancy check (CRC). Depending on the owner or use of the PDCCH, the CRC is masked with various identifiers (IDs) (e.g., radio network temporary identifier (RNTI)). For example, if the PDCCH is for a specific UE, the CRC is masked by the UE ID (e.g., cell RNTI (C-RNTI)). If the PDCCH is used for a paging message, the CRC is masked by the paging RNTI (P-RNTI). If the PDCCH is used for system information (e.g., system information block (SIB)), the CRC is masked by the system information RNTI (SI-RNTI). When the PDCCH is used for RAR, the CRC is masked by a random access RNTI (RA-RNTI).

[0075] The PDCCH includes 1, 2, 4, 8 or 16 control channel elements (CCEs) depending on its aggregation level (AL). A CCE is a logical allocation unit used to provide a specific code rate for the PDCCH depending on the radio channel state. A CCE includes 6 resource element groups (REGs), each REG being defined by one OFDM symbol multiplied by one (P)RB. The PDCCH is transmitted in a control resource set (CORESET). A CORESET is defined as a set of REGs with a given parameter set (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE can overlap with each other in the time / frequency domain. The CORESET can be configured by system information (e.g., Master Information Block (MIB)) or UE-specific higher layer signaling (e.g., Radio Resource Control (RRC) signaling). Specifically, the number of RBs and the number of symbols (up to 3) in a CORESET can be configured by higher layer signaling.

[0076] For PDCCH reception / detection, the UE monitors PDCCH candidates. PDCCH candidates are CCEs that the UE should monitor to detect PDCCH. Depending on the AL, each PDCCH candidate is defined as 1, 2, 4, 8 or 16 CCEs. Monitoring includes (blind) decoding of PDCCH candidates. The set of PDCCH candidates decoded by the UE is defined as the PDCCH search space (SS). The SS can be 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 SSs configured by the MIB or higher layer signaling. Each CORESET is associated with one or more SSs, and each SS is associated with one CORESET. The SS can be defined based on the following parameters.

[0077] -controlResourceSetId: CORESET related to SS.

[0078] - monitoringSlotPeriodicityAndOffset: PDCCH monitoring periodicity (in time slot units) and PDCCH monitoring offset (in time slot units).

[0079] - monitoringSymbolsWithinSlot: PDCCH monitoring symbols in a slot (eg, the first symbol of a CORESET).

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

[0081] * A time (eg, time / frequency resource) at which a UE is to monitor a PDCCH candidate is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities may be configured in a time slot.

[0082] Table 3 shows the characteristics of each SS.

[0083] [Table 3]

[0084]

[0085] Table 4 shows the DCI format transmitted on the PDCCH.

[0086] [Table 4]

[0087] DCI format usage 0_0 Scheduling PUSCH in a cell 0_1 Scheduling PUSCH in a cell 0_2 Scheduling PUSCH in a cell 1_0 Scheduling PDSCH in a cell 1_1 Scheduling PDSCH in a cell 1_2 Scheduling PDSCH in a cell 2_0 Notify a group of UEs of the timeslot format 2_1 Notify a group of UEs of PRBs and OFDM symbols, where the UEs can assume no transmission for the UEs 2_2 Transmission of TPC commands for PUCCH and PUSCH 2_3 Transmission of a set of TPC commands for SRS transmission by one or more UEs

[0088] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule TB-based (or TB-level) PUSCH or code block group (CBG) (or CBG level) based PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG (or CBG level) based PDSCH (DL grant DCI). DCI format 0_0 / 0_1 can be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 can be referred to as DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to deliver dynamic slot format information (e.g., dynamic slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to deliver DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 may be delivered to a corresponding group of UEs on a group-common PDCCH, which is a PDCCH for a group of UEs.

[0089] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, while DCI format 0_1 ​​and DCI format 1_1 may be referred to as non-fallback DCI formats. In fallback DCI formats, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, the DCI size / field configuration varies in non-fallback DCI formats depending on the UE configuration.

[0090] PDSCH transmits DL data (e.g., DL shared channel transport block (DL-SCH TB)) and uses a modulation scheme such as quadrature phase shift keying (QPSK), hexadecimal quadrature amplitude modulation (16QAM), 64QAM, or 256QAM. TB is encoded into codewords. PDSCH can deliver up to two codewords. Scrambling and modulation mapping can be performed on a codeword basis, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to a resource together with a demodulation reference signal (DMRS), and an OFDM symbol signal is generated from the mapped layer with the DMRS and transmitted through the corresponding antenna port.

[0091] PUCCH delivers uplink control information (UCI). UCI includes the following information.

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

[0093] -HARQ (Hybrid Automatic Repeat Request) -ACK (Acknowledgement): A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the DL data packet has been successfully received. In response to a single codeword, a 1-bit HARQ-ACK can be sent. In response to two codewords, a 2-bit HARQ-ACK can be sent. HARQ-ACK responses include positive ACK (abbreviated as ACK), negative ACK (NACK), discontinuous transmission (DTX), or NACK / DTX. The term HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0094] -CSI (Channel State Information): Feedback information for DL ​​channels. Feedback information related to Multiple Input Multiple Output (MIMO) includes RI and PMI.

[0095] Table 5 illustrates an exemplary PUCCH format. Based on PUCCH transmission duration, PUCCH formats may be divided into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4).

[0096] [Table 5]

[0097]

[0098] PUCCH format 0 conveys up to 2 bits of UCI and is mapped in a sequence-based manner for transmission. Specifically, the UE sends specific UCI to the BS by sending one of multiple sequences on the PUCCH of PUCCH format 0. Only when the UE sends a positive SR, the UE sends the PUCCH of PUCCH format 0 in the PUCCH resources used for the corresponding SR configuration.

[0099] PUCCH format 1 transmits up to 2 bits of UCI in the time domain and uses an orthogonal cover code (OCC) in the time domain to spread the modulation symbols of the UCI, which is configured differently depending on whether frequency hopping is performed. DMRS is transmitted using symbols other than modulation symbols (i.e., transmitted using time division multiplexing (TDM)).

[0100] PUCCH format 2 carries more than 2 bits of UCI, and the modulation symbols of the DCI are transmitted with the DMRS using frequency division multiplexing (FDM). The DMRS is located in symbols #1, #4, #7, and #10 of a given RB with a density of 1 / 3. A pseudo-noise (PN) sequence is used for the DMRS sequence. For 2-symbol PUCCH format 2, frequency hopping can be activated.

[0101] PUCCH format 3 does not support UE multiplexing in the same PRBS and conveys more than 2 bits of UCI. In other words, the PUCCH resources of PUCCH format 3 do not include OCC. Modulation symbols and DMRS are transmitted in time-division multiplexing (TDM).

[0102] PUCCH format 4 supports multiplexing of up to four UEs in the same PRBS and conveys more than two bits of UCI. In other words, the PUCCH resources of PUCCH format 3 include OCC. Modulation symbols and DMRS are transmitted in time-division multiplexing (TDM).

[0103] The PUSCH delivers UL data (e.g., UL shared channel transport blocks (UL-SCH TBs)) and / or UCI based on a CP-OFDM waveform or a DFT-s-OFDM waveform. When the PUSCH is transmitted with a DFT-s-OFDM waveform, the UE transmits the PUSCH with transform precoding. For example, when transform precoding is not possible (e.g., disabled), the UE can transmit the PUSCH with a CP-OFDM waveform, and when transform precoding is possible (e.g., enabled), the UE can transmit the PUSCH with a CP-OFDM waveform or a DFT-s-OFDM waveform. PUSCH transmission can be dynamically scheduled by a UL grant in the DCI, or semi-statically scheduled (configured scheduling or configured grant) by higher layer (e.g., RRC) signaling (and / or layer 1 (L1) signaling such as PDCCH). PUSCH transmission can be performed in a codebook-based or non-codebook-based manner.

[0104] Figure 5 Figure 1 shows an exemplary ACK / NACK transmission process. Figure 5, the UE can detect the PDCCH in time slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or DCI format 1_1). The PDCCH indicates the DL assignment-to-PDSCH offset (DL assignment-to-PDSCH offset) K0 and the PDSCH-to-HARQ-ACK reporting offset (PDSCH-to-HARQ-ACK reporting offset) K1. For example, DCI format 1_0 and DCI format 1_1 may include the following information.

[0105] - Frequency domain resource assignment: indicates the RB set assigned to PDSCH

[0106] - Time domain resource assignment: Indicates K0 and the starting position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH in the time slot

[0107] -PDSCH to HARQ_feedback timing indicator: indicates K1

[0108] -HARQ process number (4 bits): Indicates the HARQ process ID of the data (e.g., PDSCH or TB)

[0109] After receiving the PDSCH in slot #(n+K0) according to the scheduling information of slot #n, the UE may transmit UCI on the PUCCH in slot #(n+K1). The UCI may include a HARQ-ACK response to the PDSCH. Figure 5 Based on the assumption that the SCS of PDSCH is equal to the SCS of PUCCH, and time slot #n1=time slot #(n+K0), for the sake of convenience, it should not be understood as limiting the present invention. When the SCS is different, K1 can be indicated / interpreted based on the SCS of PUCCH.

[0110] When the PDSCH is configured to carry a maximum of 1 TB, the HARQ-ACK response can be configured in one bit. When the PDSCH is configured to carry up to two TBs, the HARQ-ACK response can be configured in two bits if spatial bundling is not configured, and can be configured in one bit if spatial bundling is configured. When slot #(n+K1) is designated as the HARQ-ACK transmission timing for multiple PDSCHs, the UCI transmitted in slot #(n+K1) includes the HARQ-ACK responses for the multiple PDSCHs.

[0111] Whether the UE should perform spatial bundling for HARQ-ACK responses may be configured for each cell group (e.g., via RRC / higher layer signaling). For example, spatial bundling may be configured for each individual HARQ-ACK response sent on the PUCCH and / or for HARQ-ACK responses sent on the PUSCH.

[0112] Spatial bundling may be supported when up to two (or two or more) TBs (or codewords) may be received at a time (or schedulable by one DCI) in the corresponding serving cell (e.g., when the higher layer parameter maxNrofCodeWordsScheduledByDCI indicates 2 TBs). More than four layers may be used for 2-TB transmission, and up to four layers may be used for 1-TB transmission. As a result, when spatial bundling is configured for the corresponding cell group, spatial bundling may be performed for serving cells in the cell group that may schedule more than four layers. A UE that wants to send a HARQ-ACK response via spatial bundling may generate a HARQ-ACK response by performing a (bitwise) logical AND operation on A / N bits for multiple TBs.

[0113] For example, assuming that a UE receives a DCI that schedules two TBs and receives the two TBs on the PDSCH based on the DCI, the UE performing spatial bundling can generate a single A / N bit by performing a logical AND operation between the first A / N bit for the first TB and the second A / N bit for the second TB. As a result, when both the first TB and the second TB are ACK, the UE reports an ACK bit value to the BS, and when at least one of the TBs is NACK, the UE reports a NACK bit value to the BS.

[0114] For example, when only one TB is actually scheduled in a serving cell configured to receive two TBs, the UE may generate a single A / N bit by performing a logical AND operation on the A / N bits for one TB and a bit value 1. As a result, the UE reports the A / N bits for one TB to the BS.

[0115] Multiple parallel DL HARQ processes exist at the BS / UE for DL ​​transmissions. These multiple parallel HARQ processes enable continuous DL transmission while the BS is waiting for HARQ feedback indicating the successful or failed reception of a previous DL transmission. Each HARQ process is associated with a HARQ buffer in the media access control (MAC) layer. Each DL HARQ process manages state variables such as the number of MAC physical data units (PDUs) transmitted, HARQ feedback for the MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0116] Figure 6 Figure 1 shows an exemplary PUSCH transmission process. Figure 6 , the UE can detect the PDCCH in time slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or 1_1). DCI format 1_0 or 1_1 can include the following information.

[0117] - Frequency domain resource assignment: indicates the RB set assigned to the PUSCH.

[0118] -Time domain resource assignment: Indicates the slot offset K2 and the duration (e.g., number of OFDM symbols) and starting position (e.g., OFDM symbol index) of the PUSCH in a slot. The starting symbol and length of the PUSCH can be indicated by the start and length indicator value (SLIV) or separately.

[0119] Then, according to the scheduling information in time slot #n, the UE can transmit PUSCH in time slot #(n+K2). PUSCH includes UL-SCH TB.

[0120] Figure 7 Figure 1 illustrates exemplary UCI multiplexing in PUSCH. When multiple PUCCH resources overlap with PUSCH resources in a slot and simultaneous PUCCH-PUSCH transmission is not configured in the slot, UCI can be sent on PUSCH (UCI piggybacking or PUSCH piggybacking) as shown. Figure 7 In the illustrated case, HARQ-ACK and CSI are carried in PUSCH resources.

[0121] Configured License (CG)

[0122] A semi-statically configured grant (CG) may be configured for a UE via RRC signaling. A maximum of 12 active CGs may be configured for a UE with respect to the corresponding BWP of the serving cell.

[0123] Each CG can be Type 1 or Type 2. Type 1 CGs can be activated / deactivated independently between serving cells. When multiple Type 2 CGs are configured, each Type 2 CG can be activated individually through DCI. One DCI can deactivate one Type 2 CG or multiple Type 2 CGs.

[0124] For CG-based transmissions in NR-U (i.e., shared spectrum channel access), the configured Grant Uplink Control Information (CG-UCI) is sent on the CG PUSCH (i.e., PUSCH scheduled by the CG). In NR-U, multiplexing between the PUCCH carrying CG-UCI and the PUCCH carrying HARQ-ACK can be configured / allowed by the BS. When the PUCCH carrying HARQ-ACK overlaps with the CG PUSCH in the PUCCH group, the multiplexing between the PUCCH carrying CG-UCI and the PUCCH carrying HARQ-ACK may not be configured. In this case, the CG PUSCH transmission is discarded.

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

[0126] Figure 8 The figure shows a wireless communication system supporting an unlicensed band. For convenience, a cell operating in a licensed band (hereinafter referred to as the L-band) is defined as an LCell, and the carrier of the LCell is defined as a (DL / UL) LCC. A cell operating in an unlicensed band (hereinafter referred to as the U-band) is defined as a UCell, and the carrier of the UCell is defined as a (DL / UL) UCC. The carrier of a cell may represent the operating frequency (e.g., center frequency) of the cell. A cell / carrier (e.g., CC) may be generally referred to as a cell.

[0127] When carrier aggregation is supported, a UE can send and receive signals to and from a BS in multiple aggregated cells / carriers. If multiple CCs are configured for a UE, one CC can be configured as a primary CC (PCC) and the other CCs can be configured as secondary CCs (SCCs). Specific control information / channels (e.g., CSS PDCCH and PUCCH) can be configured to send and receive signals only in the PCC. Data can be sent and received in the PCC and / or SCC. Figure 8 In (a), the UE and the BS transmit and receive signals in the LCC and UCC (non-standalone (NSA) mode). In this case, the LCC can be configured as a PCC and the UCC can be configured as an SCC. If multiple LCCs are configured for the UE, one specific LCC can be configured as a PCC and the other LCCs can be configured as SCCs. Figure 8 (a) Corresponds to LAA of the 3GPP LTE system. Figure 8(b) illustrates a case where the UE and BS transmit and receive signals in one or more UCCs without LCC (SA mode). In this case, one of the UCCs can be configured as a PCC, and the other UCCs can be configured as SCCs. To this end, PUCCH, PUSCH, and PRACH transmissions can be supported. Both NSA mode and SA mode are supported in the unlicensed band of the 3GPP NR system.

[0128] Unless otherwise stated, the following definitions apply to the terms as used in this disclosure.

[0129] – Channel: A carrier or a portion of a carrier including contiguous RBs for performing a channel access procedure (CAP) in a shared spectrum.

[0130] – Channel Access Procedure (CAP): A procedure for evaluating channel availability based on sensing before signal transmission to determine whether the channel is used by other communication nodes. The basic unit for sensing is a sensing slot with a duration Tsl of 9us. When the BS or UE senses the channel during the sensing slot duration and the power detected for at least 4us within the sensing slot duration is less than the energy detection threshold XThresh, the sensing slot duration Tsl can be considered to be idle. Otherwise, the sensing slot duration Tsl of 9us can be considered to be busy. CAP can be called Listen Before Talk (LBT).

[0131] – Channel occupancy: Transmissions on the channel from the BS / UE after the CAP.

[0132] – Channel Occupancy Time (COT): The total time that a BS / UE and any BS / UE sharing the channel transmit on the channel after the BS / UE's corresponding CAP. When determining the COT, if a transmission gap is less than or equal to 25 μs, the gap duration may also be included in the COT. The COT can be shared for transmissions between a BS and the corresponding UE.

[0133] -DL transmission burst: A collection of transmissions from a BS without any gaps greater than 16 us. Transmissions from a BS separated by gaps greater than 16 us are considered separate DL transmission bursts. The BS may perform transmissions after gaps within a DL transmission burst without sensing channel availability.

[0134] UL transmission burst: A collection of transmissions from a UE without any gaps greater than 16 us. Transmissions from a BS separated by gaps greater than 16 us are considered separate UL transmission bursts. The BS may perform transmissions after gaps within a UL transmission burst without sensing channel availability.

[0135] – Discovery burst: A DL transmission burst that includes a set of signals and / or channels confined within a window and associated with a duty cycle. In LTE-based systems, a discovery burst may be a BS-initiated transmission that includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS), and further includes a non-zero power CSI-RS. In NR-based systems, a discovery burst may be a BS-initiated transmission that includes at least one SS / PBCH block and further includes a CORESET for a PDCCH scheduling a PDSCH with SIB1, a PDSCH carrying SIB1, and / or a non-zero power CS-RS.

[0136] Figure 9 The figure illustrates a method for occupying resources in an unlicensed band. Depending on regional regulations regarding unlicensed bands, communication nodes in the unlicensed band need to determine whether other communication nodes are using the channel before transmitting signals. Specifically, the communication node may first perform carrier sensing (CS) before transmitting signals to check whether other communication nodes are transmitting signals. If it is determined that other communication nodes are not transmitting signals, this means that a clear channel assessment (CCA) has been confirmed. When there is a predefined CCA threshold or a CCA threshold configured through higher-layer (e.g., RRC) signaling, if energy detected in the channel exceeds the CCA threshold, the communication node may determine that the channel is busy; otherwise, the communication node may determine that the channel is idle. For reference, in the Wi-Fi standard (802.11ac), the CCA threshold is set to -62dBm for non-Wi-Fi signals and -82dBm for Wi-Fi signals. Upon determining that the channel is idle, the communication node may begin transmitting signals in the UCell. The above process may be referred to as listen-before-talk (LBT) or a channel access procedure (CAP). LBT and CAP are used interchangeably.

[0137] In Europe, two LBT operations are defined: Frame-Based Equipment (FBE) and Load-Based Equipment (LBE).

[0138] refer to Figure 10 In FBE-based LBT, a fixed frame consists of a channel occupancy time (e.g., 1 to 10 ms) and an idle period corresponding to at least 5% of the channel occupancy time. The channel occupancy time is a period during which a communication node can continue to transmit once it succeeds in channel access, and CCA is defined as an operation of monitoring the channel during a CCA time slot (at least 20 us) at the end of the idle period. The communication node periodically performs CCA based on the fixed frame. When the channel is not occupied, the communication node transmits during the channel occupancy time, and when the channel is occupied, the communication node delays transmission and waits until the CCA time slot in the next cycle.

[0139] refer to Figure 11 , in LBE-based LBT, the communication node can set q∈{4,5,...,32} and then perform CCA for one CCA slot. When the channel is not occupied in the first CCA slot, the communication node can ensure a time period of up to (13 / 32)q ms and send data within the time period. When the channel is occupied in the first CCA slot, the communication node randomly selects N∈{1,2,...,q}, stores the selected value as the initial value, and then senses the channel state based on the CCA slot. Each time the channel is not occupied in the CCA slot, the communication node decrements the stored counter value by 1. When the counter value reaches 0, the communication node can ensure a time period of up to (13 / 32)q ms and send data.

[0140] Table 6 illustrates exemplary CAPs supported in NR-U.

[0141] [Table 6]

[0142]

[0143] In 3GPP standardization, Type 1 CAP may be referred to as Category 4 (CAT4)-LBT, Type 2A CAP and Type 2B CAP may be referred to as CAT2-LBT, and Type 2C CAP may be referred to as CAT1-LBT. CAT2-LBT (i.e., Type 2A CAP and Type 2B CAP) is an FBE-based LBT, and CAT4-LBT is an LBE-based LBT.

[0144] Referring to Table 6, the BS may perform one of the following CAPs to transmit a DL signal in an unlicensed band.

[0145] (1) Type 1DL CAP

[0146] In a Type 1 DL CAP, the duration spanned by a sensing slot sensed as idle before a DL transmission is random.The Type 1 DL CAP is applicable to the following transmissions.

[0147] - a transmission initiated by the BS, comprising (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

[0148] - BS-initiated transmissions with (i) only a discovery burst or with (ii) a discovery burst multiplexed with non-unicast information.

[0149] Will refer to Figure 12The Type 1 DL CAP in Table 6 is described in more detail. The BS may sense whether the channel is idle during the time slot duration of the sensing delay duration Td, and then when the counter N is zero, the BS may perform transmission (S1234). The counter N is adjusted by sensing the channel during the additional sensing time slot duration according to the following process:

[0150] Step 1) (S1220) Set N=Ninit, where Ninit is a random number uniformly distributed between 0 and CWp, and proceed to step 4.

[0151] Step 2) (S1240) If N>0 and the BS chooses to decrement the counter, then set N=N-1.

[0152] Step 3) (S1250) Sense the channel during the additional sensing slot duration, and if the additional sensing slot duration is idle (Y), proceed to step 4; otherwise, proceed to step 5.

[0153] Step 4) (S1230) If N=0 (Y), stop (S1232); otherwise (N), go to step 2.

[0154] Step 5) (S1260) The channel is sensed until a busy sensing slot is detected within the additional delay duration Td or all sensing slots are detected as idle within the additional delay duration Td.

[0155] Step 6) (S1270) If the channel is sensed to be idle during all sensing time slots of the additional delay duration Td(Y), proceed to step 4; otherwise, proceed to step 5.

[0156] (2) Type 2DL CAP

[0157] In Type 2A / 2B DL ​​CAP, when a channel is sensed to be idle during a sensing duration of at least 25 us, the BS can perform DL transmission in the unlicensed band immediately after sensing is completed. In Type 2C DL CAP, the BS can immediately access the channel without sensing.

[0158] As previously described with reference to Table 6, multiple CAP types (i.e., LBT types) may be defined for UL transmission in the unlicensed band. For example, a Type 1 CAP or a Type 2 CAP may be defined for UL transmission. The UE may perform a CAP (e.g., Type 1 or Type 2) configured / indicated by the BS for UL signal transmission.

[0159] (1) Type 1 UL CAP

[0160] refer to Figure 13, the Type 1 UL CAP of Table 6 will be described in more detail. For signal transmission in the unlicensed band, the UE may initiate a CAP (S1510). The UE may randomly select a backoff counter N within the CW according to step 1. N is set to an initial value Ninit (S1520). Ninit is a value randomly selected between 0 and CWp. Subsequently, when the backoff counter value N is 0 (S1530; yes) according to step 4, the UE ends the CAP (S1532). The UE may then send a Tx burst (S1534). On the other hand, if the backoff counter value is not 0 (S1530; no), the UE decrements the backoff counter value by 1 according to step 2 (S1540). Subsequently, the UE checks whether the channel of the UCell is idle (S1550). If the channel is idle (S1550; yes), the UE checks whether the backoff counter value is 0 (S1530). On the other hand, if the channel is not idle, that is, the channel is busy (S1550; No), the UE checks whether the channel is idle for a deferral duration Td (25 usec or longer) that is longer than the time slot duration (e.g., 9 usec) according to step 5 (S1560). If the channel is idle for the deferral duration (S1570; Yes), the UE can resume the CAP. The deferral duration may include a duration of 16 μsec followed by Mp consecutive time slot durations (e.g., 9 μsec). On the other hand, if the channel is busy during the deferral duration (S1570; No), the UE checks whether the channel is idle for the new deferral duration by performing step S1560 again.

[0161] Table 7 shows the m used for CAP p 、Minimum CW CW min,p , Maximum CW CW max,p , Maximum Channel Occupancy Time (MCOT) T ulmcot,p The and allowed CW sizes vary according to the channel access priority level.

[0162] [Table 7]

[0163]

[0164] The CW size (CWS) applied to the Type 1 CAP can be determined in various ways. For example, the CWS can be adjusted based on whether the new data indicator (NDI) value of at least one HARQ process associated with the HARQ process ID, HARQ_ID_ref of the UL-SCH is switched within a predetermined time period (e.g., a reference TU). In the case where the UE performs signal transmission on a carrier by using a Type 1 CAP associated with a channel access priority level p, when the NDI value for at least one HARQ process associated with the HARQ_ID_ref is switched, the UE sets the CW size for all priority levels p∈{1,2,3,4} p =CW min,p Otherwise, the UE increments the CWp of all priority levels p∈{1,2,3,4} to the next higher allowed value.

[0165] Reference frame n ref (or reference time slot n ref ) is determined as follows.

[0166] When the UE is in subframe (or time slot) n g When a UL grant is received in the subframe (or time slot) n0, n1, ..., n w Starting from subframe (or time slot) n0 in the reference subframe (or time slot) n ref It is subframe (or time slot) n0.

[0167] (2) Type 2 UL CAP

[0168] When the sensing duration T is at least 25us short_ul When the sensing channel is idle during the period, the UE can perform UL transmission (e.g., PUSCH) in the unlicensed band immediately after the sensing is completed. short_ul It can be T sl (=9us)+T f (=16us).

[0169] Figure 14 An exemplary case in which a plurality of LBT sub-bands (LBT-SBs) are included in an unlicensed band is illustrated. Figure 14, multiple LBT-SBs may be included in the BWP of a cell (or carrier). For example, an LBT-SB may have a 20 MHz band. An LBT-SB may include multiple consecutive (P)RBs in the frequency domain and may be referred to as a (P)RB set. Although not shown, a guard band (GB) may be included between the LBT-SBs. Therefore, the BWP may be configured in the form of {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-SBs / RBs may be configured / defined to be indexed gradually increasing from a lower frequency band to a higher frequency band.

[0170] UE-initiated / BS-initiated COT-based transmission operations for unlicensed band operations

[0171] To support U-band (e.g., shared spectrum) operation based on FBE, a fixed frame period (FFP) starting with a BS-initiated COT (e.g., type 2A / 2B CAP) has been introduced in NR Rel-16. Table 8 summarizes the core of the FFP transmission structure.

[0172] [Table 8]

[0173]

[0174] As described in Table 8, the length of the FFP duration can be configured (semi-statically) to the UE via higher layer signaling (e.g., RRC). The term FFP used herein can be simply replaced by period or semi-static period. In addition, FFP-based channel occupancy can be referred to as semi-static channel occupancy.

[0175] In Rel-17, an FFP transmission structure starting with UE-initiated COT can be introduced to efficiently support URLLC services in a U-band environment based on FBE. In this context, an FBE transmission operation method is proposed considering both UE-initiated COT and base station-initiated COT. In the following description, DL signal may refer to a specific DL signal, and the base station may be, but is not limited to, a 5G NR base station, i.e., a gNB.

[0176] [1] Operation based on whether the UE detects DL signals in FBE operation

[0177] For the FBE operation based on the UE-initiated COT and the FBE operation based on the BS-initiated COT, the following UE / BS transmission operations can be basically considered.

[0178] 1) In addition to information about the period and start time of FFP that can start with BS-initiated COT (hereinafter referred to as "FFP-g" or "BS FFP"), information about the period and start time of FFP that can start with UE-initiated COT (hereinafter referred to as "FFP-u" or "UE FFP") can also be configured for the UE.

[0179] A. Therefore, the FFB-g of the BS can be configured to overlap with the FFP-u configured for multiple UEs in the time domain.

[0180] 2) The UE may be configured to perform LBT shortly before the start time of its FFP-u (eg, for 25 μsec, 9 μsec, or 16 μsec).

[0181] A. If, as a result of LBT, the UE determines that the channel is idle, the UE may start FFP-u transmission in a UE-initiated COT.

[0182] i. BS operation may be defined where the BS is allowed to perform DL transmission (in a shared COT) in the same FFP-u period only if the BS successfully detects a specific UL signal (e.g., PUSCH / PUCCH DMRS, PRACH, or SRS) from the UE during the duration of the FFP-u.

[0183] B. Otherwise, when the UE determines that the channel is busy, the UE may perform Rel-16 operations (e.g., Table 8), assuming (for FFP-g periods including the FFP-u start time) an FFP-g transmission structure starting with a BS-initiated COT.

[0184] i. Specifically, it may be defined that only when the UE successfully detects a specific DL signal from the BS during the FFP-g period, the UE is allowed to perform configured UL (e.g., PRACH or PUSCH) transmission in the same FFP-g period. If the UE fails to detect a DL signal during the FFP-g period, UL transmission may not be allowed.

[0185] 3) Alternatively, the UE may detect a DL signal from the BS in an FFP-g period prior to the start time of FFP-u (in an FFP-g period including the start time of FFP-u).

[0186] A. When the UE fails to detect a DL signal, the UE may perform LBT shortly before the start time of FFP-u (eg, for 25 μsec, 9 μsec, or 16 μsec).

[0187] i. When the UE determines that the channel is idle as a result of LBT, the UE may start sending FFP-u in a UE-initiated COT.

[0188] ii. When the UE determines that the channel is busy as a result of LBT, UE operation may be defined in which the UE does not perform any transmission (and / or reception) in the FFP period, or the UE may perform Rel-16 operation (e.g., Table 8), assuming an FFP-g transmission structure starting with BS-initiated COT.

[0189] B. When the UE successfully detects the DL signal, the UE may perform Rel-16 operations (eg, Table 8), assuming an FFP-g transmission structure starting with BS-initiated COT.

[0190] C. For example, before starting FFP-u transmission / UE-initiated COT configuration, the UE may attempt to detect a DL signal in the time domain based on the previous FFP-g (including the start time of FFP-u), and prioritize the shared COT based on the DL signal detection. For example, when the UE is able to share the previous BS-initiated COT and transmit its UL signal in the BS-initiated COT, the UE may discard the UE-initiated COT configuration (and LBT for it). The UE performs its UL signal transmission based on the sharing of the previous BS-initiated COT.

[0191] In this FBE operation scenario, the following UE transmission operation methods may be considered depending on whether the UE detects a DL signal from the BS.

[0192] 1) Problematic situations

[0193] A. When a specific UE (UE1) detects a DL signal from a base station (BS) during a specific FFP-g period, depending on whether the DL signal is transmitted based on the BS-initiated COT or based on the UE-initiated COT of another UE (UE2), UE1 may be allowed to transmit the configured UL resources (e.g., CGPUSCH, PRACH, PUCCH, or SRS) configured in FFP-g (after the detected DL signal) (when the DL signal is transmitted using the BS-initiated COT) or may not be allowed to transmit the configured UL resources (when the DL signal is transmitted in a shared COT based on the UE-initiated COT). However, if the UE's determination of this is inconsistent with the BS's intention, the UE may violate FBE operation-related regulations or cause certain interference situations. For example, although the BS performs DL transmissions using the UE-initiated COT shared with UE2, UE1 may misunderstand that the DL signal is transmitted based on the BS-initiated COT and perform UL transmission using the configured UL resources configured in FFP-g, causing problems such as signal collisions. A problem may occur when UE1 performs UL transmission that it would not have performed if UE1 had known that the DL signal was transmitted based on sharing of the UE-initiated COT for UE2.

[0194] 2) Proposal 1

[0195] A. In the case where the BS performs DL signal transmission with a shared COT based on the UE-initiated COT generated by UE2, when the configured UL resources of UE1 are configured in the period of FFP-g of the BS (overlapping with or including the DL signal transmission time), the BS can be specified to operate as in the following option 1 / 2.

[0196] i. Option 1: The BS may configure / transmit only signals that UE1 should not receive / detect (i.e., signals that UE1 should not detect or determine to be transmitted based on BS-initiated COT) as DL signals. The BS operation may include, but is not limited to, at least one of the following: (i) not transmitting broadcast signals / channels, (ii) not transmitting unicast signals / channels related to UE1 (e.g., UE-specific PDCCH / PDSCH) or UE group common (GC) PDCCH / PDSCH (carrying control information / data), (iii) transmitting unicast signals / channels related to UE2 (carrying control information / data), and / or (iv) transmitting GC-PDCCH / PDSCH (carrying control information / data) not related to UE1.

[0197] ii. Option 2: The BS operation may be defined such that the BS only configures / transmits unicast signals / channels (carrying control information / data) related to UE2 as DL signals. For example, it may be specified that the BS is not allowed to transmit broadcast signals / channels and GC-PDCCH / PDSCH.

[0198] B. As a similar operation method, the following i. Option A to iv. Option D will be described under the assumption that the BS performs DL signal / channel transmission with a shared COT based on the UE-initiated COT generated by UE2.

[0199] i. Option A

[0200] 1. When (from the perspective of the BS) there are UL resources configured / scheduled only for UE2 or there are no UL resources configured / scheduled for any UE during the period of FFP-g including the DL transmission time (or the remaining duration of FFP-g after the DL transmission time), any UE can receive DL signals / channels from the BS without restriction on the target receiver. For example, all (or at least some) of the unicast PDCCH / PDSCH / signal for UE2, the unicast PDCCH / PDSCH / signal for UEs other than UE2, the UE-specific GCPDCCH / PDSCH / signal, and the broadcast PDCCH / PDSCH / signal can be transmitted as DL signals / channels.

[0201] 2. Otherwise, when (from the BS's perspective) there are UL resources configured / scheduled for UEs other than UE2 in the duration of FFP-g including the DL transmission time (or the remaining duration of FFP-g after the DL transmission time), the target receiver of the DL signal / channel transmitted by the BS may be limited to UE2. For example, a unicast PDCCH / PDSCH / signal only for UE2 may be transmitted as a DL signal / channel.

[0202] ii. Option B

[0203] 1. When (from the perspective of the BS) there are UL resources configured / scheduled only for UE2 in the duration of FFP-g including the DL transmission time (or the remaining duration of FFP-g after the DL transmission time), there are no UL resources configured / scheduled for any UE, or there are UL resources scheduled for UEs other than UE2 only for transmission based on UE-initiated COT indicated by DCI, any UE can receive DL signals / channels from the BS without restriction on the target receiver.

[0204] 2. Otherwise, when (from the perspective of the BS) there are UL resources configured for UEs other than UE2 or UL resources scheduled for transmission based on BS-initiated COT indicated by DCI for UEs other than UE2 in the duration of FFP-g including the DL transmission time (or the remaining duration of FFP-g after the DL transmission time), the target receiver of the DL signal / channel sent by the BS may be limited to UE2.

[0205] iii. Option C

[0206] 1. When (from the BS's perspective) there are no UL resources configured / scheduled for any UE in the duration of FFP-g including the DL transmission time (or the remaining duration of FFP-g after the DL transmission time), any UE can receive DL signals / channels from the BS without restriction on the target receiver.

[0207] 2. Otherwise, when (from the BS's perspective) there are UL resources configured / scheduled for any UE in the duration of FFP-g including the DL transmission time (or the remaining duration of FFP-g after the DL transmission time), the target receiver of the DL signal / channel sent by the BS may be limited to UE2.

[0208] iv. Option D: Regardless of whether there are specific UL resources in the duration of FFP-g including the DL transmission time (or the remaining duration of FFP-g after the DL transmission time), the target receiver of the DL signal / channel transmitted by the BS may always be limited to UE2.

[0209] 3) Proposal 2

[0210] A. Depending on whether the configured UL resources (e.g., UL resources semi-statically / semi-persistently configured through RRC signaling, such as CG PUSCH, PRACH, or PUCCH) and / or scheduled UL resources (e.g., UL resources dynamically indicated / scheduled through DCI, etc.) (e.g., their starting symbols) are aligned with the start time of FFP-u (time alignment), different energy detection threshold (EDT) values ​​can be set for transmission of UL resources in LBT.

[0211] i. For example, a single EDT value (hereinafter, "EDT_sh") (e.g., a value separately set by the BS) may be fixedly used for UL resources aligned (time-aligned) with the start time of FFP-u. For UL resources not aligned (time-aligned) with the start time of FFP-u, another specific single EDT value (hereinafter, "EDT_no_sh") (e.g., a value calculated based on the UE maximum transmission power, etc.) may be fixedly used, or at least one of multiple EDT values ​​(e.g., EDT_sh and EDT_no_sh) may be selected and applied by the UE (and the selected / applied EDT value may be signaled by the UE to the BS in the UL resources). For example, when FFP-u is configured for a specific UE, EDT_sh may always be configured for that UE. For example, it may be specified that when the BS wants to allow FFP-u configuration for a specific UE, the BS should signal EDT_sh to the specific UE.

[0212] ii. (In an example related to the above example,) when the UE generates / configures a UE-initiated COT through UL transmission to which EDT_sh is applied, the UE may perform additional (configured) UL transmissions within the period of FFP-u starting with the UE-initiated COT (or the UE may be allowed to perform additional UL transmissions based on the UE-initiated COT).

[0213] iii. (In an example related to the above example,) when the BS receives a transmission from the UE in UL resources based on EDT_sh, the BS may (regarding the UL transmission as based on the COT initiated by the UE) perform DL transmission in the shared COT after the UL resources (or the BS may be allowed to perform DL transmission in the shared COT). When the BS receives a transmission from the UE in UL resources based on EDT_no_sh, the BS does not perform DL transmission in the shared COT after the UL resources (or the BS may not be allowed to perform DL transmission in the shared COT) (without regard- ing the UL transmission as based on the COT initiated by the UE).

[0214] 4) Proposal 3

[0215] A. Even if the configured UL resources (e.g., CG PUSCH, PRACH, or PUCCH) and / or scheduled UL resources (e.g., PUSCH or PUCCH) (e.g., their starting symbols) are aligned with the start time of FFP-u (time alignment), different EDT values ​​may be set for transmission of UL resources in LBT, depending on whether the UL transmission is based on UE-initiated COT.

[0216] ii. For example, when UL transmission is based on a UE-initiated COT, a single EDT value (e.g., EDT_sh) may be fixedly used. When UL transmission is based on a shared COT based on a BS-initiated COT, another specific single EDT value (e.g., EDT_no_sh) may be fixedly used, or at least one of a plurality of EDT values ​​(e.g., EDT_sh and EDT_no_sh) may be selected and applied by the UE (and the selected / applied EDT value may be signaled by the UE to the BS in UL resources). (When FFP-u is configured for a UE, EDT_sh may always be configured for the UE.)

[0217] ii. (In an example related to the above example,) when the UE generates / configures a UE-initiated COT through UL transmission to which EDT_sh is applied, the UE may perform additional (configured) UL transmission in the period of FFP-u starting with the UE-initiated COT (or the UE may be allowed to perform additional UL transmission based on the UE-initiated COT).

[0218] iii. (In an example related to the above example,) when the BS receives transmission from the UE in UL resources to which EDT_sh is applied, the BS may (regarding the UL transmission as being based on the COT initiated by the UE) perform DL transmission in the shared COT after the UL resources (or the BS may be allowed to perform DL transmission in the shared COT). When the BS receives transmission from the UE in UL resources to which EDT_no_sh is applied, the BS does not perform DL transmission in the shared COT after the UL resources (without regard- ing the UL transmission as being based on the COT initiated by the UE) (or the BS may not be allowed to perform DL transmission in the shared COT).

[0219] 5) Proposal 4

[0220] A. Using the configured UL resources (e.g., CGPUSCH, PRACH, and / or PUCCH) and / or scheduled UL resources (e.g., PUSCH and / or PUCCH) aligned with the start time of FFP-u (e.g., their starting symbols), one of a plurality of EDT values ​​(e.g., EDT_sh and EDT_no_sh) may be configured / indicated by the BS or selected and applied by the UE as the EDT value applied when the UE generates / configures UE-initiated COT through corresponding UL transmission.

[0221] i. (In an example related to the above example,) when the UE generates / configures a UE-initiated COT through UL transmission to which EDT_sh is applied, the UE may perform additional (configured) UL transmission in the period of FFP-u starting with the UE-initiated COT (or the UE may be allowed to perform additional UL transmission based on the UE-initiated COT).

[0222] ii. (In an example related to the above example,) when the UE generates / configures a UE-initiated COT through UL transmission to which EDT_sh is applied, the UE may perform an additional (configured) UL transmission in a period of FFP-u starting with the UE-initiated COT (or the UE may be allowed to perform an additional UL transmission based on the UE-initiated COT) or the UE may not perform an additional (configured) UL transmission in a duration of FFP-u starting with the UE-initiated COT (or the UE may not be allowed to perform an additional UL transmission based on the UE-initiated COT).

[0223] iii. (In an example related to the above example,) when the BS receives transmission from the UE in UL resources to which EDT_sh is applied, the BS may perform DL transmission in the shared COT after the UL resources (or the BS may be allowed to perform DL transmission in the shared COT). When the BS receives transmission from the UE in UL resources to which EDT_no_sh is applied, the BS may not perform DL transmission in the shared COT after the UL resources (or the BS may not be allowed to perform DL transmission in the shared COT).

[0224] [2] Sending configured UL resources from UE in FBE operation scenario

[0225] 1) Problematic situations

[0226] A. Depending on whether the configured UL resources (e.g., CGPUSCH, PRACH, and / or PUCCH) (e.g., with a start symbol) configured to be aligned with the start time of FFP-u are transmitted based on the UE-initiated COT or are transmitted in a shared COT based on the BS-initiated COT (for convenience, defined as "shared BS COT" transmission), subsequent operations and effects may vary.

[0227] B. When under the assumption of UE-initiated COT (e.g. Figure 15 ) sends the configured UL (hereinafter referred to as "C-UL") resources (e.g., Figure 15 1) in FFP-u (e.g., Figure 15 However, when C-UL#1 is transmitted in the shared BS COT under the assumption of BS-initiated COT, transmission of another C-UL resource (C-UL#x) whose end time overlaps with the idle period F5 may be allowed. Figure 15 The period of FFP-g#1) in the Figure 15The transmission of another C-UL resource (C-UL#x) overlaps with the idle period at the end time of FFP-u#1. (Case 1-1)

[0228] C. When (such as Figure 15 As shown in the figure, in the same situation as above, when UE-initiated COT transmission is assumed / performed for C-UL#1, the BS may not be allowed to transmit a DL signal so as to overlap with the idle period F5 at the end time of FFP-u#1. However, when shared BS COT transmission is assumed / performed for C-UL#1, the BS may be allowed to transmit a DL signal so as to overlap with the idle period F5 at the end time of FFP-u#1. (Case 1-2)

[0229] D. When Figure 15 In the illustrated scenario, when shared BS COT transmission is assumed / performed for C-UL#1 aligned with the start time of FFP-u#1, transmission of C-UL#2 configured in FFP-u#2 within FFP-g#1 including C-UL#1 and immediately after FFP-u#1 in which C-UL#1 is configured may be allowed, however, when UE-initiated COT transmission is assumed / performed for C-UL#1, transmission of C-UL#2 may not be allowed (because it is outside the period of FFP-u#1 in which C-UL#1 is configured) (Case 2-1).

[0230] E. When Figure 16 In the case where shared BSCOT transmission is assumed / performed for C-UL#1 aligned with the start time of FFP-u#1, transmission of C-UL#3 configured outside the period including FFP-g#1 of C-UL#1 (although within FFP-u#2 in which C-UL#1 is configured) may not be allowed. However, when UE-initiated COT transmission is assumed / performed for C-UL#1, transmission of C-UL#3 may be allowed (because it is within the period in which FFP-u#2 of C-UL#1 is configured). (Case 2-2)

[0231] F. In a situation where association / subsequent operations of the UE / BS are performed differently depending on whether UE-initiated COT transmission or shared BS COT transmission is assumed / performed for a specific C-UL resource aligned with the start time of FFP-u as described above, when the UE fails to detect a DL signal transmitted by the BS for the purpose of generating BS-initiated COT or the BS misinterprets a UL signal transmitted by the UE for the purpose of generating UE-initiated COT as being for shared BS COT transmission, operations that degrade the transmission and reception performance of the UE / BS or violate FBE-related regulations may occur.

[0232] 2) Proposal 1

[0233] A. For a specific FFP-u (e.g., Figure 16 Specific C-UL resources (e.g., Figure 16 C-UL#3) in the example, you can do the following:

[0234] i. When the UE is in FFP-g including C-UL#3 (e.g. Figure 16 When a DL signal based on a COT initiated by the BS is detected (regardless of whether the UE is an FFP-u (e.g., Figure 2 If the UE generates / configures UE-initiated COT in FFP-u#2), the UE can assume / perform shared BS COT transmission in C-UL#3. (This is defined as "Operation 1").

[0235] ii. Otherwise, when the UE fails to detect the DL signal of the COT initiated by the BS in the FFP-g, the UE is configured with C-UL#3 in the FFP-u ( Figure 16 When a UE-initiated COT is generated / configured in FFP-u#2 in C-UL#3 (this may be limited to the case where the start time of C-UL#3 does not overlap with the start time of FFP-g), the UE may assume / perform UE-initiated COT transmission in C-UL#3. (This is defined as "Operation 2").

[0236] iii. In another method, it may be provided that when the UE fails to include FFP-g ( Figure 16 When a DL signal based on BS-initiated COT is detected in FFP-g#2 (this may be limited to the case where C-UL#3 does not overlap with the start time of FFP-g), the UE does not perform transmission in C-UL#3, considering that C-UL#3 is invalid. (This is defined as "Operation 3").

[0237] B. The operation of Proposal 1 can be equally applied to scheduled UL resources. For example, "specific C-UL resources configured in FFP-u" can be replaced by "specific scheduled UL resources indicated by FFP-u", "FFP-u in which corresponding C-UL resources are configured" can be replaced by "FFP-u for which corresponding scheduled resources are indicated", and "C-UL resources" can be replaced by "scheduled UL resources".

[0238] C. It may be stipulated that when a C-UL resource not aligned with the start time of FFP-u is configured to overlap with the start time of a specific FFP-g, the UE does not perform transmission in the C-UL resource considering that the C-UL resource is invalid.

[0239] D. It may be specified that when scheduled UL resources that are not aligned with the start time of FFP-u are indicated as overlapping with the start time of a specific FFP-g, the UE applies / performs "Operation 1" and / or "Operation 2" and / or "Operation 3".

[0240] 3) Proposal 2

[0241] In the case of BS for a specific FFP-g (e.g. Figure 15 In the case of FFP-g#1) generating / configuring a BS-initiated COT, the following operations may be performed:

[0242] i. A BS may be able to send / be allowed to send DL signals to an idle period ( Figure 15 When the following operations are not performed, the BS may not be allowed to transmit a DL signal that overlaps with the idle period of a specific FFP-u within the duration of FFP-g.

[0243] 1. BS can start at the start time of FFP-g and in the idle period of FFP-u ( Figure 15 Before the idle period F5 of the end time of FFP-u#1, or shortly before the idle period FFP-u#1 Figure 15 DL signal transmission is performed before the start time of FFP-u#1 in (the UE can detect it as COT transmission initiated by the BS).

[0244] ii. A BS may be able to send / be allowed to send DL signals to a specific FFP-u ( Figure 15 When the following operations are not performed, the BS may not be allowed to transmit a DL signal that overlaps with the start time of a specific FFP-u within the duration of FFP-g.

[0245] 1. BS can start at the start time of FFP-g or at the start time of FFP-u ( Figure 15 DL signal transmission is performed before the start time of FFP-u#2 in UE (the UE can detect it as COT transmission initiated by the BS).

[0246] 4) Proposal 3

[0247] A. When the UE is configured to align with the start time of a specific FFP-u through a specific C-UL resource ( Figure 16 The transmission of C-UL#1 in Figure 15In the case of FFP-u#1) generating / configuring UE-initiated COT, the following operations can be performed:

[0248] i. It may be stipulated that when a specific FFP-g ( Figure 16 When the start time of FFP-g#2 in the UE is included in the duration of FFP-u, the UE detects a DL signal transmitted based on the COT initiated by the BS in FFP-g#2 (the UE determines whether the DL signal has been transmitted).

[0249] 1. It is specified that upon detection of a DL signal, the UE operates under the assumption of a BS-initiated COT (e.g., assumes / performs UL transmission in a shared BS COT) in a period (e.g., UL resources configured / scheduled in this period) within the duration of FFP-u that overlaps with the period of FFP-g#2 (or after the time when the DL signal is detected).

[0250] 2. It may be stipulated that when the UE fails to detect a DL signal, the UE assumes / performs UL transmission based on the UE-initiated COT in a period (e.g., at least C-UL resources) that overlaps with the period of FFP-g#2 within the duration of FFP-u (or after the time when the DL signal is detected), or considers / assumes that the C-UL resources configured in this period are invalid and does not perform a transmission operation in the C-UL resources.

[0251] ii. Alternatively, it may be specified that when a specific FFP-g ( Figure 16 When the start time of FFP-g#2 in FFP-g#2 is included in the duration of FFP-u, considering / assuming that the C-UL resources are invalid (regardless of whether a DL signal is detected in FFP-g#2), the UE does not perform transmission in the C-UL resources configured in a period overlapping with the period of FFP-g#2 (or after the time when the DL signal is detected).

[0252] iii. Therefore, it may be specified that the UE assumes / performs UL transmission based on UE-initiated COT only in a period (e.g., at least C-UL resources) until the earlier of the end time of the duration of FFP-u (from the start time of the duration of FFP-u) and the end time of the duration of FFP-g (e.g., a time X μsec (e.g., X=9 or 16 or 25) before the start time of the period of FFP-g immediately after the duration of FFP-g).

[0253] 1. Therefore, when the end time of the duration of FFP-g (e.g., a time that is X μsec (e.g., X=9, 16, or 25) before the start time of the duration of FFP-g immediately after the end time of the duration of FFP-u) is earlier than the end time of the duration of FFP-u, transmission based on the UE-initiated COT may be impossible in C-UL resources belonging to the duration of FFP-u and outside the duration of FFP-g (or a period until a time that is X μsec (e.g., X=9, 16, or 25) before the start time of the duration of FFP-g immediately after the duration of FFP-g) (UL transmission in the shared BS COT may be possible in the C-UL resources only based on detection of a DL signal transmitted in the BS-initiated COT).

[0254] B. Alternatively, in a specific FFP-u (e.g. Figure 16 The start time of the FFP-u#2) in the specific FFP-g ( Figure 16 1) in the FFP-g#1 period, and a specific C-UL resource (e.g., Figure 16 In the case where C-UL#1 in the FFP-u is configured to be aligned with the start time of FFP-u#2, the following operations may be performed:

[0255] i. When C-UL#1 overlaps with a specific DL signal / channel (e.g., SSB to be broadcast (resources for SS / PBCH transmission)) and / or a specific CORESET (e.g., with the lowest ID / index) (configured by MIB / SIB) resource configured to be sent in FFP-g#1, the operation of generating UE-initiated COT through the transmission of C-UL#1 may not be allowed.

[0256] 1. Therefore, it may be stipulated that UL transmission in the shared BS COT is possible in the period of FFP-u#2 (including C-UL#1) only based on detection of DL signals transmitted in the BS-initiated COT.

[0257] 5) Proposal 4

[0258] A. For any C-UL resource or specific C-UL resource configured to be aligned with the start time of a specific FFP-u (e.g., configured to enable / allow generation / configuration of UE-initiated COT through corresponding C-UL transmission), the following operations may be performed:

[0259] i. When the time interval between the start time of FFP-u or the start symbol of the C-UL resource and the time when the previous DL signal is detected (e.g., the DL-to-UL gap) is equal to or greater than X μsec (e.g., X=9, 16, or 25) (or the time corresponding to the idle period configured in FFP-u), the UE may generate / configure a UE-initiated COT through the transmission of C-UL resources. (That is, it may be specified that the generation / configuration of the UE-initiated COT is enabled / permitted through the transmission of C-UL resources.)

[0260] ii. It may be stipulated that when the time interval between the start time of FFP-u or the start symbol of the C-UL resource and the time when the previous DL signal is detected (e.g., DL to UL gap) is less than X μsec (e.g., X=9 or 16 or 25) (or a time corresponding to an idle period configured in FFP-u), the UE does not generate / configure a UE-initiated COT through transmission of the C-UL resources, wherein only shared BS COT transmission is enabled / allowed in the C-UL resources, or considering that the C-UL resources are invalid, the UE does not perform a transmission operation in the C-UL resources.

[0261] B. It may be stipulated that for C-UL resources that are not configured to enable / allow (through corresponding C-UL transmission) generation / configuration of UE-initiated COT, the UE is only enabled / allowed to perform shared BSCOT transmission.

[0262] 6) Proposal 5

[0263] A. For C-UL resources configured to be aligned with the start time of any FFP-u or a specific FFP-u (e.g., configured to enable / allow UE-initiated generation / configuration of COT), the following operations may be performed:

[0264] i. When the time interval between the start time of FFP-u or the start symbol of the C-UL resource and the time when the previous DL signal is detected (e.g., the DL-to-UL gap) is equal to or greater than X μsec (e.g., X=9, 16, or 25) (or the time corresponding to the idle period configured in FFP-u), the UE may generate / configure a UE-initiated COT through the transmission of C-UL resources. (That is, it may be specified that the generation / configuration of the UE-initiated COT is enabled / permitted through the transmission of C-UL resources.)

[0265] ii. It may be stipulated that when (the C-UL resource is included in the period of a specific FFP-g, and) the time interval between the start time of FFP-u or the start symbol of the C-UL resource and the time when the previous DL signal is detected (e.g., DL to UL gap) is less than X μsec (e.g., X=9 or 16 or 25) (or a time corresponding to an idle period configured in FFP-u), the UE does not generate / configure a UE-initiated COT through transmission of the C-UL resource, wherein only shared BS COT transmission is enabled / allowed in the C-UL resource, or considering that the C-UL resource is invalid, the UE does not perform a transmission operation in the C-UL resource.

[0266] B. It may be specified that for C-UL resources configured to be aligned with the start time of an FFP-u that is not configured to enable / allow UE-initiated COT generation / configuration, the UE is only enabled / allowed to perform shared BS COT transmission.

[0267] C. The operation of Proposal 5 can be applied similarly to scheduled UL resources. For example, "C-UL resources configured to be aligned with the start time of FFP-u" can be replaced with "scheduled UL resources indicated to be aligned with the start time of FFP-u", and "C-UL resources" can be replaced with "scheduled UL resources".

[0268] 7) Proposal 6

[0269] A. A specific FFP-u (boundary) set may or may not be configured for the UE. When a specific FFP-u set is configured for the UE, the following operations may be performed:

[0270] i. For C-UL resources configured to be aligned with the start time of an FFP-u belonging to a specific FFP-u set, only shared BS COT transmission may be enabled / allowed.

[0271] ii. For C-UL resources configured to be aligned with the start time of an FFP-u that does not belong to a specific FFP-u set, the following operations may be performed.

[0272] -Alt-1

[0273] 1. When the time interval between the start time of FFP-u or the start symbol of the C-UL resource and the time when the previous DL signal is detected (e.g., DL to UL gap) is equal to or greater than X μsec (e.g., X=9, 16, or 25) (or the time corresponding to the idle period configured in FFP-u), the UE may generate / configure a UE-initiated COT through the transmission of the C-UL resource. (That is, the generation / configuration of the UE-initiated COT may be enabled / permitted through the transmission of the C-UL resource.)

[0274] 2. Otherwise, when (the C-UL resource is included in the period of a specific FFP-g, and) the time interval between the start time of FFP-u or the start symbol of the C-UL resource and the time when the previous DL signal is detected (e.g., DL to UL gap) is less than X μsec (e.g., X=9 or 16 or 25) (or a time corresponding to an idle period configured in FFP-u), the UE may not generate / configure a UE-initiated COT through transmission of the C-UL resource, wherein only shared BS COT transmission is enabled / allowed in the C-UL resource, or the UE may not perform a transmission operation in the C-UL resource considering that the C-UL resource is invalid.

[0275] -Alt-2

[0276] 1. When no DL signal is detected at the start time of the corresponding FFP-u or before the start symbol of the corresponding C-UL resource (in the period of the specific FFP-g) (the corresponding C-UL resource is included in the period of the specific FFP-g), the UE may generate / configure a UE-initiated COT by transmitting the C-UL resource. (That is, the generation / configuration of the UE-initiated COT may be enabled / permitted by the transmission of the corresponding C-UL resource.)

[0277] 2. Otherwise, when a DL signal is detected at the start time of the corresponding FFP-u or before the start symbol of the corresponding C-UL resource (in the period of the specific FFP-g) (the corresponding C-UL resource is included in the period of the specific FFP-g), the UE may not perform a transmission operation in the C-UL resource considering that the C-UL resource is invalid.

[0278] B. Otherwise, when no specific FFP-u set is configured for the UE, the operations of Alt-1 or Alt-2 may be applied to C-UL resources configured to be aligned with the start time of any FFP-u.

[0279] C. The above-described operating method can be similarly applied to scheduled UL resources. (In an example related to the above example,) this 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 indicated as aligned with the start time of FFP-u" and replacing "C-UL resources" with "scheduled UL resources."

[0280] D. A specific FFP-u (boundary) set can be configured in the following method.

[0281] i. Alt-a: A specific FFP-u (boundary) set may be configured as (all or) a specific portion (e.g., by a bitmap) of an FFP-u set belonging to an X-msec period (e.g., X=20 or X=10) including the first FFP-u after the start (boundary) time of an even radio frame number / index (e.g., 0), and the FFP-u set configuration may be equally applied every X msec.

[0282] ii. Alt-b: A specific FFP-u (boundary) set may be configured as (all or) a specific portion (e.g., by a bitmap) of the Y FFP-u sets including (including) the first FFP-u after the start (boundary) time of an even radio frame number / index (e.g., 0), and the FFP-u set configuration may be applied equally to every Y FFP-u.

[0283] E. In the case of a specific FFP-u set, the UE may be configured with a single FFP-u set that is common to (and generally applies to) the configured UL resources and the scheduled UL resources, or a separate FFP-u set for (applying to) each of the configured UL resources and the scheduled UL resources.

[0284] [3] UL / DL transmission in the idle period of the FFP period in the FBE operation scenario

[0285] 1) Problematic situation 1

[0286] A. For FFP-u starting with its UE-initiated COT transmission, the UE may operate as follows:

[0287] - Case U1) The UE may not be allowed to perform UL transmission in the idle period of FFP-u.

[0288] - Case U2) The UE may be allowed to perform UL transmission in the idle period of FFP-g included in the duration of FFP-u.

[0289] B. For FFP-g starting with BS-initiated COT transmission, the UE can operate as follows:

[0290] - Case N1) The UE may not be allowed to perform UL transmission in the idle period of FFP-g (based on the shared BSCOT).

[0291] - Case N2) The UE may be allowed to perform UL transmission in the idle period of FFP-u included in the duration of FFP-g (based on the shared BS COT).

[0292] C. When there is a mismatch between the UE and the BS at the corresponding time regarding the COT initiator (e.g., the UE or the BS) in case U2 (and / or case N2), unexpected interference may affect the UE and the BS (and / or each UE). Interference can be easily controlled in scheduled UL transmission by indicating an appropriate transmission time through DCI, but it may not be easy to control interference in UL transmission of a specific configuration (e.g., CG PUSCH).

[0293] 2) Proposal 1

[0294] A. Option 1

[0295] i. It may be specified that in case U2, only scheduled UL transmission may be allowed, while configured UL transmission may not be allowed.

[0296] 1. Therefore, considering that the idle period of FFP-g corresponding to case U2 is invalid for the configured UL transmission, the UE may configure and transmit the configured UL resources.

[0297] ii. Alternatively, in case U2, the UE may be configured to determine whether UL transmission is allowed for the configured UL transmission.

[0298] B. Option 2

[0299] i. It may be stipulated that in case N2, only UL transmission (based on the shared BS COT) is allowed for scheduled UL transmission, and UL transmission (based on the shared BS COT) is not allowed for configured UL transmission.

[0300] 1. Therefore, considering that the idle period of FFP-g corresponding to case N2 is invalid for the configured UL transmission, the UE may configure and transmit the configured UL resources.

[0301] ii. Alternatively, in case N2, the UE may be configured to determine whether UL transmission (based on shared BSCOT) is allowed for the configured UL transmission.

[0302] C. Option 3

[0303] i. It may be stipulated that in case U2 and case N2, UL transmission may be allowed only for scheduled UL transmission, and not allowed for configured UL transmission.

[0304] 1. Therefore, considering that the idle period of FFP-g corresponding to case U2 and the idle period of FFP-u corresponding to case N2 are invalid for the configured UL transmission, the UE may configure and transmit the configured UL resources.

[0305] ii. Alternatively, whether UL transmission is allowed for the configured UL transmission may be configured for the UE in case U2 and case N2.

[0306] D. Note: At least CG PUSCH may be included in the configured UL resources.

[0307] 3) Problematic situation 2

[0308] A. For FFP-g starting with BS-initiated COT transmission, the BS can operate as follows:

[0309] - Case A1) The BS may not be allowed to perform DL transmission in the idle period of FFP-g.

[0310] - Case A2) The BS may be allowed to perform DL transmission in the idle period of FFP-u included in the duration of FFP-g.

[0311] B. For FFP-u starting with UE-initiated COT transmission, the BS can operate as follows:

[0312] - Case B1) The BS may not be allowed to perform DL transmission in the idle period of FFP-u (based on the shared BS COT).

[0313] - Case B2) The BS may be allowed to perform DL transmission in the idle period of FFP-g included in the duration of FFP-u (based on the shared BS COT).

[0314] C. When there is a mismatch between the UE and the BS at the corresponding time regarding the COT initiator (e.g., the UE or the BS) in case A2 (and / or case B2), unexpected interference may affect the UE and the BS (and / or each UE). Interference can be easily controlled in scheduled DL transmission by indicating an appropriate transmission time through DCI, but it may not be easy to control interference in DL transmission of specific configurations (e.g., SPS PDSCH).

[0315] 4) Proposal 2

[0316] A. Option 1

[0317] i. It may be specified that in case A2, the UE performs DL reception only for scheduled DL transmissions and not for configured DL transmissions.

[0318] 1. Therefore, considering that the idle period of FFP-u corresponding to case A2 is invalid for the configured DL transmission, the UE can configure and receive the configured DL resources.

[0319] ii. Alternatively, whether to perform configured DL reception for configured DL transmission may be configured for the UE in case A2.

[0320] B. Option 2

[0321] i. It may be specified that in case B2, the UE performs DL reception only for scheduled DL transmission (based on the shared BS COT) and not for configured DL transmission (based on the shared BS COT).

[0322] 1. Therefore, considering that the idle period of FFP-g corresponding to case B2 is invalid for the configured DL transmission, the UE can configure and receive the configured DL resources.

[0323] ii. Alternatively, the UE may be configured in case B2 whether to perform DL reception for the configured DL transmission (based on the shared BS COT).

[0324] C. Option 3

[0325] i. It may be specified that in case A2 and case B2, the UE performs DL transmission only for scheduled DL transmission and not for configured DL transmission.

[0326] 1. Therefore, considering that the idle period of FFP-u corresponding to case A2 and the idle period of FFP-g corresponding to case B2 are invalid for the configured DL resources, the UE may configure and transmit the configured DL resources.

[0327] ii. Alternatively, whether to perform DL reception for the configured DL transmission may be configured for the UE in case A2 and case B2.

[0328] D. Note: At least SPS PDSCH may be included in the configured DL resources.

[0329] [4] UE operation for scheduled UL transmission in FBE operation scenario

[0330] 1) In case whether scheduled UL (eg, PUSCH or PUCCH) transmission is performed based on UE-initiated COT or based on shared COT (which is based on BS-initiated COT) is indicated through DCI, the following UE operations may be considered.

[0331] A. When scheduled UL (e.g., PUSCH / PUCCH / SRS) resources are indicated to the UE through UL / DL scheduling DCI and the UE is instructed to perform transmission in the scheduled UL resources, for example, based on the shared COT (scheduled UL transmission based on the BS-initiated COT in the period of FFP-g), option 1) the UE may perform shared COT transmission in the scheduled UL resources by assuming that the BS has already started BS-initiated COT transmission in the FFP-g including the scheduled UL resources (while skipping the DL signal detection / sensing process or regardless of whether a DL signal / the result of DL signal detection is detected), or option 2) the UE may perform UL transmission in the scheduled UL resources based on the shared COT only when (as a result of DL signal detection / sensing) the UE detects a DL signal (sent based on the BS-initiated COT) in the FFP-g including the scheduled UL resources, however, when the UE fails to detect the DL signal (as a result of DL signal detection / sensing in the FFP-g including the scheduled UL resources), the UE may discard the scheduled UL transmission.

[0332] B. In an example of operation of Option 1, when cell 1 carrying DCI is different from cell 2 in which scheduled UL resources are allocated (for example, DCI of cell 1 is configured to schedule PUSCH in cell 2 through cross-carrier scheduling and / or when HARQ-ACK feedback for DCI / PDSCH transmission in cell 1 is transmitted on PUCCH of cell 2), and the transmission time of DCI is limited to the duration of FFP-g in which scheduled UL resources are allocated (for example, FFP-g of cell 2) (or the duration of FFP-g including the DCI transmission time overlaps in time with the duration of FFP-g of cell 2 including the scheduled UL resources), the UE / BS can transmit / receive UL signals based on Option 1.

[0333] C. In an example of operation of Option 2, when cell 1 carrying DCI is different from cell 2 to which scheduled UL resources are allocated, and (and / or) the transmission time of the DCI is not limited to the duration of the FFP-g to which the scheduled UL resources are allocated (e.g., FFP-g of cell 2) (or the duration of FFP-g including the DCI transmission time does not temporally overlap with the duration of FFP-g of cell 2 including the scheduled UL resources) (for convenience, this case is defined as "Case A"), the UE / BS may transmit / receive UL signals based on Option 2. DL signal detection (for confirming that the BS reserves / occupies FFP-g in a cross-carrier scheduling scenario (e.g., for confirming the start of a BS-initiated COT) may be performed in cell 2 to which the scheduled UL resources are allocated. The operation of Option 2 may not necessarily be limited to cross-carrier scheduling. In the example of operation of Option 2, Option 2 may also be applied when the cell carrying DCI is the same as the cell to which scheduled UL resources are allocated. For example, when the cell carrying the DCI is the same as the cell in which the scheduled UL resources are allocated, and the scheduled UL resources are not restricted within the FFG-g carrying the DCI, the UE / BS may apply Option 2.

[0334] D. When it is indicated by a specific (eg, UE group common) DCI that the FFP-g period of cell 2 allocated with UL resources is available for DL ​​transmission / reception, the operation of option 1 may be exceptionally applied.

[0335] Figure 17 is a diagram illustrating UL signal transmission / reception according to an embodiment of the present disclosure. As previously described, to perform scheduled UL transmission in a shared COT, the UE should (basically) check whether the BS successfully occupies / guarantees the corresponding FFP-g (e.g., the BS starts with a BS-initiated COT), and can perform UL transmission only after completing the BS's DL transmission in the FFP-g that the BS successfully occupies / guarantees, using the remaining duration of the shared FFP-g. However, when it is determined that Option 1 (exceptional) applies, the UE may skip operation H20 of confirming that the BS has successfully occupied / guaranteed the FFP-g.

[0336] refer to Figure 17, the UE receives DCI (H10). The DCI may be, but is not limited to, a UL grant DCI that schedules UL transmissions. For example, because a PUCCH transmission by the UE in the PUCCH resources indicated by the DL grant DCI is also a scheduled UL transmission, the DCI may also be a DL grant DCI. The FFP carrying the DCI is assumed to be FFP_a. FFP_a may be FFP-g starting with a BS-initiated COT. The DCI may indicate channel access parameters for UL transmissions. Based on the DCI, the UE may determine whether the scheduled UL transmission is for FFP-g (the BS-initiated COT corresponding to FFP-g) or FFP-u (the UE-initiated COT corresponding to FFP-u). The UE may determine whether to perform channel sensing for the scheduled UL transmission based on network signaling (e.g., DCI). Hereinafter, it is assumed that the UL transmission scheduled by DCI (starting with a BS-initiated COT) is included in FFP_g, and the UE is instructed to perform the scheduled UL transmission in the shared COT in FFP-g starting with the BS-initiated COT.

[0337] Upon receiving the DCI, the UE checks whether the scheduled UL resources are restricted within the FFP_a in which the DCI has been received (H15).

[0338] When the scheduled UL resources are included in FFP_a, in other words, when the scheduled UL transmission is scheduled in the same FFP as the DCI (e.g., intra-period scheduling), the UE can perform UL transmission (H25) based on Option 1 scheduling. UL transmission based on Option 1 scheduling can be performed based on the shared COT. In UL transmission based on Option 1 scheduling, the UE can skip the DL detection / sensing process for determining whether the FFP is FFP-g starting with the BS-initiated COT. Figure 18 is a diagram illustrating an exemplary case of UL transmission based on shared COT. For example, Figure 18 Can be used with Figure 17 H25 or H30 related. Figure 18 , the UE determines whether to perform the scheduled UL transmission within a time gap of up to 16 us from the previous UL transmission time (in the case where there is a UL transmission before the scheduled UL transmission) (J15). For example, when there is any UL transmission performed before the time gap of up to 16 us from the scheduled UL transmission, the UE may perform the scheduled UL transmission without additional channel sensing (LBT). In the absence of any UL transmission performed before the time gap of up to 16 us from the scheduled UL transmission, the UE may perform additional channel sensing (LBT) (J20), and when it is determined that the channel is idle, perform the scheduled UL transmission (J30).

[0339] Return Reference Figure 17 , when the scheduled UL resources are not included in FFP_a, in other words, when the scheduled UL resources are scheduled in FFP_a different from the FFP carrying the DCI (e.g., cross-period scheduling), the UE can perform UL transmission based on the scheduling of Option 2 (H15, No). According to Option 2, the UE should perform a DL detection / sensing process for FFP_b to which the scheduled UL resources belong (H20). When FFP_a carries DCI, it is not obvious to the UE / BS whether FFP_b can be occupied by the BS. This is because the corresponding spectrum is a shared spectrum / unlicensed band and therefore needs to coexist with other devices / standards (e.g., IEEE802.11, etc.). For example, even if it is agreed in advance that FFP_b is configured as FFP-g starting with a BS-initiated COT (e.g., at the latest at FFP_a), a third device that does not comply with the 3GPP standard or a third device that is unaware of the pre-agreement between the 3GPP UE and the BS is likely to occupy FFP_b. For example, 3GPP BS / UE does not have the right to exclusively occupy the frequency band, and therefore cannot completely exclude the possibility that a third device occupies FFP_b. Therefore, the UE should check whether the BS has actually successfully occupied FFP_b at the start time of FFP_b to which the scheduled UL resources belong. In other words, the UE needs to perform a DL detection / sensing process at the start time of FFP_b to check for the presence of a DL signal related to the COT initiated by the BS (H20). In the case that there is no DL signal related to the COT initiated by the BS at the start time of FFP_b (H20, failed), the UE is not sure whether FFP_b is occupied by the BS (in other words, there is a possibility that a third device occupies FFP_b), and therefore does not perform scheduled UL transmission that may conflict with the third device (H25, discard). In the case that there is a DL signal related to the COT initiated by the BS at the start time of FFP_b (H20, passed), the UE performs scheduled UL transmission based on the shared COT, determines that FFP_b is occupied / reserved by the BS (H30 and Figure 18 ).

[0340] E. It is further possible to consider whether the DCI overlaps with the scheduled UL resources in the time domain (intra-period scheduling) and whether the DCI overlaps with the scheduled UL resources in the frequency domain (intra-frequency scheduling). In addition, when the cell carrying the (UL / DL grant) DCI is the same as the cell allocated with the scheduled UL (e.g., PUSCH / PUCCH / SRS) resources, it is possible to consider whether option 1 / 2 should be applied.

[0341] For example, even if the transmitted cell is the same as the cell in which the scheduled UL resources are allocated, option 2 may be applied when one or more RB sets (requiring separate / independent LBT) are configured in the corresponding cell.

[0342] Alternatively, in the case where the cell carrying the DCI is the same as the cell in which the scheduled UL resources are allocated, when one or more RB sets are configured in the corresponding cell, the operation of option 1 and the operation of option 2 may be separately applied as follows.

[0343] i. In the example of operation of Option 1, when RB set 1 carrying DCI is different from RB set 2 to which scheduled UL resources (corresponding to DCI) are allocated, and DCI transmission and scheduled UL resources are included in the same FFP-g period (i.e., intra-period scheduling), the UE / BS may operate based on Option 1. For example, referring to Figure 20 (a), based on the fact that the scheduled UL resources (indicated as being related to the COT initiated by the BS) are limited to the period of FFP-g#j carrying the DCI, (even if RB set #a≠RB set #c), the UE / BS can transmit / receive UL signals based on option 1. For example, referring to Figure 20 (b), the scheduled UL resources (indicated as being related to the BS-initiated COT) are completely restricted to the period of FFP-g#x carrying the DCI (for example, the start and end of the scheduled UL resources are completely included in FFP-g#x), (even if carrier #a ≠ carrier #b,) the UE / BS can transmit / receive UL signals based on Option 1.

[0344] ii. In the example of operation of Option 2, even when the RB set carrying DCI is the same as the corresponding RB set to which the scheduled UL resources are allocated (i.e., intra-frequency scheduling), UL signals can be transmitted and received based on Option 2, and Option 2 is not necessarily restrictively applied to DCI and scheduled UL resources in different RB sets. For example, when (DCI and scheduled UL resources belong to different RB sets, and) DCI transmission and scheduled UL resources are not included in the same FFP-g period (i.e., included in different FFP-g periods) (e.g., cross-period scheduling and cross-frequency scheduling. For convenience, this case is defined as "Case B"), the UE / BS can operate based on Option 2. In this case, DL signal detection (e.g., Figure 19 H20a) in the above may mean detecting DL signals centrally in RBs to which scheduled UL resources are allocated.

[0345] iii. (Regardless of the situation in case B,) when it is indicated by a DCI of a specific format (e.g., UE group common DCI) that the FFP-g period in RB set 2 to which scheduled UL resources are allocated is available for DL ​​transmission / reception, the operation of option 1 may be exceptionally applied.

[0346] F. Figure 19 is a diagram illustrating UL signal transmission / reception according to an embodiment of the present disclosure. Figure 19 can be understood as specifying the previously described Figure 17 In other words, because Figure 17 yes Figure 19 So Figure 19 and Figure 17 There is no conflict between them. Figure 19 yes Figure 17 , so Figure 17 The description is not to be construed as Figure 19 However, this can be avoided with Figure 17 The description is repeated Figure 19 Description. The UE receives DCI that schedules UL transmission (e.g., UL grant DCI or DL ​​grant DCI) (H10a). It is assumed that the FFP carrying the DCI is FFP_a. FFP_a may be FFP-g starting with a BS-initiated COT. The DCI may indicate channel access parameters for UL transmission. The UE may determine based on the DCI whether the scheduled UL transmission is for FFP-g (BS-initiated COT corresponding to FFP-g) or FFP-u (UE-initiated COT corresponding to FFP-u). The UE may determine whether to perform channel sensing for the scheduled UL transmission based on network signaling (e.g., DCI). In the following description, it is assumed that the UL transmission scheduled by DCI is included in FFP-g (starting with a BS-initiated COT), and the UE is instructed to perform the scheduled UL transmission in a shared COT in FFP-g starting with a BS-initiated COT.

[0347] Upon receiving the DCI, the UE checks whether the scheduled UL resources are (completely) restricted to the FFP_a carrying the DCI (intra-period scheduling) or in the frequency resource region (eg, RB set or carrier) carrying the DCI (intra-frequency scheduling) ( H15a ).

[0348] In case of intra-period and intra-frequency scheduling, the UE may perform UL transmission based on the scheduling of option 1 ( Figure 18 For example, the operation of the UE / BS based on Option 1 (for example, when DCI is received in the RB set in which UL resources are allocated, the DL signal detection process is skipped) can be performed in the same frequency resource region (RB set / carrier) and the same FFP-g.

[0349] In case of cross-period scheduling and cross-frequency scheduling, the UE may perform UL transmission based on scheduling of option 2 (H15a, No).

[0350] exist Figure 18In the case of cross-period scheduling or cross-frequency scheduling, the UE is exemplarily implemented to perform UL transmission based on the scheduling of option 2, which should not be interpreted as limiting the present disclosure, and the UE may operate as follows (the following i / ii may be understood as not distinguishing between cross-frequency scheduling and intra-frequency scheduling). Figure 17 Similar results were obtained for the embodiment of FIG.

[0351] i. For example, (in the case of intra-period scheduling and cross-frequency scheduling) the UE may perform UL transmission based on scheduling according to Option 1 based on intra-period scheduling. Option 1 may be applied when DCI is transmitted in frequency resource #1 (e.g., RB set / carrier #1) and the transmission time of the DCI in frequency resource region #1 is included in the FFP-g period of frequency resource region #2 (e.g., RB set / carrier #2) to which scheduled UL resources are allocated. (Herein, RB set / carrier #1 and RB set / carrier #2 may be the same or different).

[0352] ii. For example, (in the case of inter-period scheduling and intra-frequency scheduling or inter-period scheduling and same frequency) the UE may perform UL transmission based on the scheduling of Option 2 based on inter-period scheduling. Option 2 may be applied when DCI is transmitted in frequency resource region #1 (e.g., RB set / carrier #1) and the transmission time of the DCI in frequency resource region #1 is not included in the FFP-g period of frequency resource region #2 (e.g., is located before the start time of the FFP-g period).

[0353] 2) In the case where the DCI indicates whether the scheduled UL transmission is performed based on the UE-initiated COT or the shared COT (DCI indicates the transmission type), the following UE operations may be additionally considered.

[0354] A. In the case where transmission based on UE-initiated COT is indicated by DCI for a specific scheduled UL resource (e.g., which is not aligned with the start time of a specific FFP-u period and which is allocated to be included in the FFP-u period), when the UE has started UE-initiated COT transmission in the FFP-u period at a previous time, the UE may send the scheduled UL resource based on the UE-initiated COT, otherwise, the transmission in the scheduled UL resource is discarded.

[0355] B. In the case where transmission based on the shared COT is indicated by DCI for specific scheduled UL resources (e.g., which are allocated to be included in the FFP-g period), when the UE has started shared COT transmission in the FFP-g period at a previous time, the UE may transmit the scheduled UL resources based on the shared COT (while skipping a DL signal detection operation in the cell in which the scheduled UL resources are allocated or regardless of whether a DL signal is detected in the cell), and otherwise, apply Option 1 or Option 2 (depending on cross-carrier scheduling / indication of each cell and the presence or absence of the FFP-g period).

[0356] [5] Processing operations related to the determination of the COT initiator in the case of FBE operations

[0357] In the case where a carrier (i.e., cell) including multiple RB sets and / or multiple cells (including one or more RB sets) are configured for the UE (i.e., CA scenario), the following operations can be considered for determining the COT initiator (e.g., UE-initiated COT or BS-initiated COT) (from the UE's perspective).

[0358] A. In an RB set group including a plurality of RB sets configured in the same cell (e.g., intra-carrier scheduling) or the same BWP (and / or a cell (RB set) group including a plurality of cells (multiple RB sets in a cell) configured in the same frequency band (e.g., intra-band scheduling)), for a specific FFP-g period, in the absence of an RB set for which BS-initiated COT (or UL transmission (e.g., scheduled UL transmission) based on BS-initiated COT) is indicated (through a specific DCI (e.g., UE-specific or UE group-common DCI)), in which a corresponding DL signal (sent based on BS-initiated COT) is detected, or in the absence of an RB set for which BS-initiated COT (or UL transmission (e.g., scheduled UL transmission) based on BS-initiated COT) is indicated (through a specific DCI (e.g., UE-specific or UE group-common DCI)) is indicated (through a specific DCI (e.g., UE-specific or UE group-common DCI)). In a case where a UE-specific DCI (e.g., a broadcast SSB (resources for transmission of SS / PBCH) and / or a specific CORESET (e.g., with the lowest ID / index (configured by MIB / SIB))) is indicated as an RB set available for DL ​​transmission / reception by a UE-specific DCI), UL transmission based on UE-initiated COT may be enabled / permitted in (all or part of) the RB sets of the RB set group in an FFP-u period (and / or an FFP-u period temporally overlapping with the start time of FFP-g) or included in the FFP-g period.

[0359] i. In this case, when (for the FFP-u period), the UE-initiated COT (or UL transmission (e.g., scheduled UL transmission) based on the UE-initiated COT) is indicated by the BS for a specific RB set of an RB set group or the UE determines to assume the UE-initiated COT for a specific RB set (for UL transmission (e.g., scheduled UL transmission) allocated to the RB set), the UE can perform UL transmission in the RB set (or the RB set group to which the RB set belongs) and assume / determine the UE-initiated COT for the RB set (or the entire RB set group to which the RB set belongs).

[0360] B. In an RB set group including a plurality of RB sets configured in the same cell (e.g., intra-carrier scheduling) or the same BWP (and / or a cell (RB set) group including a plurality of cells (multiple RB sets in a cell) configured in the same frequency band (e.g., intra-band scheduling)), for a specific FFP-g period, at least one RB set for which BS-initiated COT (or UL transmission (e.g., scheduled UL transmission) based on BS-initiated COT) is indicated (through a specific DCI (e.g., UE-specific or UE group-common DCI)), at least one RB set in which a corresponding DL signal (sent based on BS-initiated COT) is detected, or at least one RB set (sent through a specific DCI (e.g., UE-specific or UE group-common DCI)) is detected. In the case where a group-common DCI or a UE-specific DCI) indicates at least one RB set (or an RB set including a specific DL signal / channel (e.g., a broadcast SSB (resource for transmission of SS / PBCH) and / or a specific CORESET (e.g., with the lowest ID / index (configured by MIB / SIB))) that can be used for DL ​​transmission / reception, UL transmission based on the UE-initiated COT may be enabled / permitted in any RB set of the RB set group in an FFP-u period that does not temporally overlap with the FFP-g period or (having a start time) is included in the FFP-g period (and / or an FFP-u period that temporally overlaps with the start time of FFP-g). (Therefore, only UL transmission based on the BS-initiated COT (based on the shared COT) may be enabled / permitted in the FFP-g period.)

[0361] i. In this case, when (for the FFP-g period) BS-initiated COT (or UL transmission based on BS-initiated COT (e.g., scheduled UL transmission)) is indicated, a corresponding DL signal (sent based on BS-initiated COT) is detected, or DL ​​transmission / reception is indicated as available, for a specific RB set of the RB set group, the UE can perform UL transmission in the RB set, assuming / determining BS-initiated COT only for this RB set.

[0362] C. In another method, for an RB group including multiple RB sets configured in the same cell (e.g., intra-carrier scheduling) (and / or a cell (RB set) group including multiple cells (including multiple RB sets in a cell) configured in the same frequency band (e.g., intra-band scheduling)), the following operations may be performed:

[0363] -In a state where a guard band is configured (e.g., intra-carrier) between adjacent RB sets in a frequency within a cell / BWP, when some specific (allocated) RB sets in an RB set group are configured / indicated as specific types of UL transmission resources (e.g., configured or scheduled resources), the following operations may be performed.

[0364] - As long as the COT initiator determined / assumed / indicated for the allocated RB set (e.g., UE-initiated COT or BS-initiated COT) is the same, UL transmission can be allowed / enabled regardless of whether the COT initiator matches the COT initiator determined / assumed / indicated for the remaining RB sets (except the corresponding allocated RB set). For convenience, this behavior is defined as "Multiple RB Set Behavior 1".

[0365] i. For example, when the COT initiator determined / assumed / indicated for the allocated RB set is also UE-initiated COT, UL transmission may be allowed / enabled even if the COT initiator determined / assumed / indicated for the remaining RB sets is BS-initiated COT.

[0366] ii. Therefore, in this case, when the COT initiator determined / assumed / indicated for the allocated RB sets differs between the RB sets, UL transmission may be disallowed / enabled. (That is, the UE may discard the UL transmission.)

[0367] iii. In a specific example, it is assumed that an RB set group including a total of N RB sets is configured (in a BWP or carrier), and the UE is to perform UL transmission on M (an integer less than or equal to N) RB sets in the RB set group. The COT initiator is determined on an RB set basis. (i) When the UL transmission that the UE intends to perform corresponds to the configured UL transmission, the COT initiators of all M RB sets should be the same (e.g., COT initiator of RB set #1 = COT initiator of RB set #2 = ... = COT initiator of RB set #M) so that the UE can perform the configured UL transmission. (ii) When the UL transmission that the UE intends to perform corresponds to the scheduled UL transmission and the COT initiator indicated by the DCI is indicated as X (where X is the UE or the BS), the COT initiators of all M RB sets should be determined to be 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) so that the UE can perform the scheduled UL transmission. For example, in (i) / (ii), UL transmission can be performed without determining the COT initiators of other RB sets (e.g., NM RB sets) (e.g., in a state where no signal is detected despite performing signal detection / sensing to determine the COT initiator, or COT initiator determination is not performed for the remaining RB sets). For example, in (i) / (ii), when the COT initiators of the M RBs are different from the COT initiators of the remaining RB sets (e.g., NM RB sets), the UE can perform an additional process for determining whether to discard the UL transmission. Alternatively, in (i) / (ii), even if the COT initiator of the M RBs is different from the COT initiator of the remaining RB sets (eg, NM RB sets), UL transmission may be performed (exceptional under specific conditions).

[0368] D. In another method, for an RB group including multiple RB sets configured in the same cell (e.g., intra-carrier scheduling) or the same BWP (and / or a cell (RB set) group including multiple cells (including multiple RB sets in a cell) configured in the same frequency band (e.g., intra-band scheduling)), the following operations may be performed:

[0369] -In a state where a guard band is configured (e.g., intra-carrier) between adjacent RB sets in a frequency within a cell / BWP, when some specific (allocated) RB sets in an RB set group are configured / indicated as specific types of UL transmission resources (e.g., configured or scheduled resources), the following operations may be performed.

[0370] -When the COT initiator A determined / assumed / indicated for the allocated RB set (e.g., UE-initiated COT or BS-initiated COT) is the same, and (in the absence or presence of a COT initiator for the remaining RB set) the COT initiator A matches the COT initiator determined / assumed / indicated for the remaining RB set (other than the allocated RB set).

[0371] i. For example, when the COT initiator determined / assumed / indicated for the allocated RB set is also the UE-initiated COT, UL transmission may be allowed / enabled even if there is no COT initiator specifically determined / assumed / indicated for the remaining RB sets.

[0372] ii. Therefore, in this case, when the COT initiator determined / assumed / indicated for the allocated RB set and the remaining RB set is different between the RB sets, UL transmission may be disallowed / enabled. (That is, the UE may discard the UL transmission.)

[0373] E. In another method, for an RB group including multiple RB sets configured in the same cell (e.g., intra-carrier scheduling) or the same BWP (and / or a cell (RB set) group including multiple cells (including multiple RB sets in a cell) configured in the same frequency band (e.g., intra-band scheduling)), the following operations may be performed:

[0374] -In a state where no (e.g., intra-carrier) guard band is configured between adjacent RB sets in a frequency within a cell / BWP, when some specific (allocated) RB sets in an RB set group are configured / indicated as specific types of UL transmission resources (e.g., configured or scheduled resources), the following operations may be performed.

[0375] - When the COT initiator A (e.g., UE-initiated COT or BS-initiated COT) determined / assumed / indicated for the allocated RB set is the same, and (in the absence or presence of a COT initiator for the remaining RB set) COT initiator A matches the COT initiator determined / assumed / indicated for the remaining RB set, UL transmission may be allowed / enabled. For convenience, this behavior is defined as "Multiple RB Set Behavior 2".

[0376] i. For example, when the COT initiator determined / assumed / indicated for the allocated RB set is also the UE-initiated COT, UL transmission may be allowed / enabled even if there is no COT initiator specifically determined / assumed / indicated for the remaining RB sets.

[0377] ii. Therefore, in this case, when the COT initiator determined / assumed / indicated for the allocated RB set and the remaining RB set is different between the RB sets, UL transmission may be disallowed / enabled. (That is, the UE may discard the UL transmission.)

[0378] In a feature example, for an RB group including multiple RB sets configured in the same cell (e.g., intra-carrier scheduling) or the same BWP (and / or a cell (RB set) group including multiple cells (including multiple RB sets in a cell) configured in the same frequency band (e.g., intra-band scheduling)), the following operations may be performed:

[0379] - When a guard band is configured (eg, intra-carrier) between adjacent RB sets in frequency in a cell / BWP, the UE may operate based on multiple RB sets behavior 1.

[0380] - When no (eg intra-carrier) guard band is configured between adjacent RB sets in frequency in a cell / BWP, the UE may operate based on multiple RB sets behavior 2.

[0381] F. In another (or additional) method, for a specific FFP-g period, in an RB set group including a plurality of RB sets configured in the same cell (e.g., intra-carrier scheduling) or the same BWP (and / or a cell (RB set) group including a plurality of cells (multiple RB sets in a cell) configured in the same frequency band (e.g., intra-band scheduling)), at least one RB set for which BS-initiated COT (or UL transmission based on BS-initiated COT (e.g., scheduled UL transmission)) is indicated (through specific DCI (e.g., UE-specific or UE group-common DCI)) and at least one RB set in which a corresponding DL signal (sent based on BS-initiated COT) is detected is detected. In the case of a B set, or at least one RB set indicated as available for DL ​​transmission / reception (by specific DCI (e.g., UE group common DCI or UE specific DCI)) (or an RB set including a specific DL signal / channel (e.g., broadcast SSB (resources for transmission of SS / PBCH) and / or a specific CORESET (e.g., with the lowest ID / index (configured by MIB / SIB))), the UE may be configured not to perform UL transmission in any RB set (among all RB sets) during the idle duration of that FFP-g (e.g., drop UL transmission (among all RB sets)) that is configured / indicated to temporally overlap with the idle period).

[0382] i. In this case, UL transmission may not be performed during the idle duration of FFP-g in both the RB set (configured for UL transmission) based on the BS-initiated COT and the RB set (configured for UL transmission) based on the UE-initiated COT (e.g., UL transmission in the corresponding RB set that is configured / indicated to temporally overlap with the idle period may be discarded).

[0383] G. In another (or additional) method, when a specific (e.g., configured or scheduled) UL transmission is configured / indicated on multiple RB sets (on the same cell / carrier), if transmission / operation based on BS-initiated COT within a specific FFP-g period is determined / assumed for some of the multiple RB sets, and if transmission / operation based on UE-initiated COT within a specific FFP-u period is determined / assumed for the remaining RB sets, the UE may be configured to drop UL transmission on the following resources: resources in all the multiple RB sets that are configured / indicated to temporally overlap with idle periods associated with FFP-g and resources (in all the multiple RB sets) that are configured / indicated to temporally overlap with idle periods associated with FFP-u.

[0384] i. In this case, the UE may be configured to drop UL transmission on resources that are configured / instructed to temporally overlap with an idle period related to FFP-g, not only for RB sets for which transmission / operation based on BS-initiated COT is determined / assumed among multiple RB sets, but also for RB sets for which transmission / operation based on UE-initiated COT is determined / assumed among multiple RB sets. Furthermore, the UE may be configured to drop UL transmission on resources that are configured / instructed to temporally overlap with an idle period related to FFP-u, not only for RB sets for which transmission / operation based on UE-initiated COT is determined / assumed among multiple RB sets, but also for RB sets for which transmission / operation based on BS-initiated COT is determined / assumed among multiple RB sets.

[0385] H. This can be done to prevent (UL to DL) interference caused by UE-initiated COT transmissions to BS-initiated COT / FFP. For example, problems such as collision / interference between BS-initiated COT and UE-initiated COT can be prevented.

[0386] 2) Additionally, in a scenario where a carrier (i.e., a cell) including multiple RB sets and / or multiple cells (including one or more RB sets) are configured, from the perspective of the BS, the following operations may be considered with respect to the determination of the COT initiator (e.g., UE-initiated COT or BS-initiated COT).

[0387] A. For a specific FFP-u period, in an RB set group including multiple RB sets configured in the same cell (e.g., intra-carrier scheduling) (and / or a cell (RB set) group including multiple cells (multiple RB sets in a cell) configured in the same frequency band (e.g., intra-band scheduling)), in the absence of an RB set indicated (through specific DCI) for BS-initiated COT (or UL transmission based on BS-initiated COT (e.g., scheduled UL transmission)) or an RB set in which a corresponding UL signal (transmitted based on UE-initiated COT) is detected, the BS may perform DL transmission based on BS-initiated COT in (all or part of) the RB sets of the RB set group in an FFP-g period that temporally overlaps with the FFP-u period or (has a start time) is included in the FFP-u period.

[0388] B. For a specific FFP-u period, in an RB set group including multiple RB sets configured in the same cell (e.g., intra-carrier scheduling) (and / or a cell (RB set) group including multiple cells (multiple RB sets in a cell) configured in the same frequency band (e.g., intra-band scheduling)), if there is at least one RB set indicated (through specific DCI) for BS-initiated COT (or UL transmission based on BS-initiated COT (e.g., scheduled UL transmission)) or at least one RB set in which a corresponding UL signal (transmitted based on UE-initiated COT) is detected, from the perspective of the BS, the BS may not temporally overlap with the FFP-u period or perform DL transmission based on BS-initiated COT in any RB set belonging to the RB set group in an FFP-g period (having a start time) included in the FFP-u period.

[0389] 3) Additionally, when the UE is configured with a carrier (ie, cell) or BWP including multiple RB sets, the following operations may be considered for determining the COT initiator (eg, determination of UE-initiated COT or BS-initiated COT) (from the UE's perspective).

[0390] A. Operation 1: For an RB set group consisting of multiple RB sets configured on the same cell (e.g., within a carrier) or on the same BWP, it is assumed that (at least) some (allocated) RB sets in the RB set group are configured / indicated as specific (e.g., configured or scheduled) UL transmission resources.

[0391] UL transmission may be allowed / enabled in the following cases: when the same COT initiator (COT initiator A (e.g., UE-initiated COT or BS-initiated COT)) is determined / assumed / indicated for the corresponding (allocated) RB set (in particular, when it is detected / confirmed that COT initiator A is indicated by DCI for all (allocated) sets when the UL transmission is a scheduled UL transmission), and when no COT initiator is determined / assumed / indicated for the remaining RB sets (except the corresponding allocated RB set) or when the COT initiator determined / assumed / indicated for the remaining RB sets (except the corresponding allocated RB set) is the same as COT initiator A.

[0392] i. For example, when the COT initiator determined / assumed / indicated for the (allocated) RB set is also used for UE-initiated COT, UL transmission may be allowed / enabled even if there is no COT initiator determined / assumed / indicated for the remaining RB sets.

[0393] ii. Therefore, in this case, if the COT initiator determined / assumed / indicated for the (allocated) RB set is different from the COT initiator determined / assumed / indicated for the remaining RB sets, UL transmission may not be enabled / allowed (the UE may be configured to drop UL transmission).

[0394] B. Operation 2: For an RB set group consisting of multiple RB sets configured on the same cell (e.g., within a carrier) or on the same BWP, it is assumed that (at least) some (allocated) RB sets in the RB set group are configured / indicated as specific (e.g., configured or scheduled) UL transmission resources.

[0395] As long as the same COT initiator (e.g., UE-initiated COT or BS-initiated COT) is configured for the corresponding (allocated) RB set (in particular, when it is detected / confirmed that the COT initiator is indicated by DCI for all (allocated) RB sets when the UL transmission is a scheduled UL transmission), UL transmission can be allowed / enabled regardless of whether the corresponding COT initiator is the same as the COT initiator determined / assumed / indicated for the remaining RB sets (except the corresponding (allocated) RB set).

[0396] i. For example, if the COT initiator determined / assumed / indicated for the corresponding (allocated) RB set is also used for UE-initiated COT, UL transmission may be allowed / enabled even if the COT initiator determined / assumed / indicated for the remaining RB sets is for BS-initiated COT.

[0397] ii. Therefore, in this case, if different COT initiators are determined / assumed / indicated for the corresponding (allocated) RB sets, UL transmission may not be allowed / enabled (that is, the UE may be configured to discard UL transmission) (for convenience, this operation is referred to as "operation 2-1"). For example, according to operation 2-1, UL transmission may not be allowed / enabled based on the fact that the first RB set and the second RB set are included in some (allocated) RB sets and the COT initiator of the first RB set is different from the COT initiator of the second RB set.

[0398] iii. Alternatively, in this case, if different COT initiators are determined / assumed / indicated for the corresponding (allocated) RB sets, UL transmission may be performed based on the UE-initiated COT (for convenience, this operation is referred to as "operation 2-2"). For example, according to operation 2-2, based on the fact that the first RB set and the second RB set are included in some (allocated) RB sets and the COT initiator of the first RB set is different from the COT initiator of the second RB set, UL transmission may be limited to being allowed / enabled only based on the UE-initiated COT.

[0399] C. Operation 3: For an RB set group consisting of multiple RB sets configured on the same cell (e.g., within a carrier) or on the same BWP, it is assumed that certain (allocated) RB sets in the RB set group are configured / indicated as specific (e.g., configured or scheduled) UL transmission resources.

[0400] UL transmission may be allowed / enabled regardless of whether the same or different COT initiators (eg, UE-initiated COT or BS-initiated COT) are determined / assumed / indicated for the corresponding (allocated) RB set.

[0401] i. For example, when the COT initiator determined / assumed / indicated for the corresponding (allocated) RB set indicates UE-initiated COT for the first RB set and BS-initiated COT for the second RB set, UL transmission may be allowed / enabled.

[0402] D. Note 1

[0403] i. When no (intra-carrier) guard band is configured between adjacent / contiguous RB sets in frequency on a cell / BWP, operation 1 may be applied. When an intra-carrier guard band is configured, operation 2 may be applied.

[0404] ii. When no (intra-carrier) guard band is configured between adjacent / contiguous RB sets in frequency on a cell / BWP, operation 1 may be applied. When an intra-carrier guard band is configured, operation 3 may be applied.

[0405] iii. When no (intra-carrier) guard band is configured between adjacent / contiguous RB sets in frequency on a cell / BWP, operation 2 may be applied. When an intra-carrier guard band is configured, operation 3 may be applied.

[0406] E. Note 2

[0407] i. When the UL transmission is a scheduled UL transmission, operation 2 may be applied, and when the UL transmission is a configured UL transmission, operation 3 may be applied.

[0408] ii. (In operation 2) When the UL transmission is a scheduled UL transmission, and when different COT initiators are determined / assumed for some (allocated) RB sets (when all COT initiators indicated by DCI do not match), the UE may apply operation 2-1 (of operation 2).

[0409] iii. (In operation 2) When the UL transmission is a configured UL transmission, and when different COT initiators are determined / assumed for some (allocated) RB sets, the UE may apply operation 2-2 (of operation 2).

[0410] Figure 21 An exemplary UL signal transmission and reception process based on determination of a COT initiator according to an embodiment of the present disclosure is illustrated. Figure 21 The embodiments are exemplary application methods proposed above, and thus do not limit the scope of the present disclosure. In addition, in order to understand Figure 21 For the embodiments, please refer to the above description.

[0411] refer to Figure 21, a COT initiator is determined for the RB set in which UL transmission is to be performed (K10). The COT initiator determination may include a process of detecting / sensing a signal. The COT initiator may be determined for each RB set. The UE may determine the COT initiator for each RB set in the FFP to which the RB set (allocated at least for UL transmission) belongs. In the case of configured UL transmission, depending on whether the COT initiators of the (allocated) RB sets are all the same (K15), the UE may perform UL transmission (K25 where the UE performs a channel access procedure (required) for UL transmission). In the case of scheduled UL transmission, the UE receives a DCI indicating a COT initiator and thereby determines whether the COT initiators of all (allocated) RB sets are the same as the COT initiator indicated by the DCI (K15). When the COT initiators of all (allocated) RB sets are the same as the COT initiator indicated by the DCI, the UE performs UL transmission (K25 where the UE performs a channel access procedure (required) for UL transmission). When it is determined that the CPT initiator of at least one (allocated) RB set is different from the COT initiator indicated by the DCI, the UE may discard the UL transmission (K20). As described above, for example, even if there is no COT initiator specifically determined / assumed / indicated for the remaining RB sets (other than the allocated RB set of the corresponding RB set group), UL transmission may be allowed / enabled. In a more specific implementation example, when the COT initiator of the allocated RB set is different from the COT initiator of the remaining RB sets, UL transmission may not be allowed / enabled. (That is, the UE may discard the UL transmission.)

[0412] [6] UE operation for configured UL transmission in FBE operation scenario

[0413] 1) When a specific configured UL transmission (resource) starts after a specific FFP-u period starts (that is, the specific configured UL transmission (resource) is not aligned with the start of the corresponding FFP-u) and the specific configured UL transmission (resource) is configured to overlap with an idle period of the specific FFP-u period, the following UE operation may be considered.

[0414] A. If the UE has generated a UE-initiated COT for FFP-u (if the UE performs UL transmission based on the UE-initiated COT when the corresponding FFP-u starts), the UE may be configured to discard the configured UL transmission (for convenience, this is defined as "Case 1").

[0415] B. Otherwise, when the UE does not generate a UE-initiated COT for FFP-u (e.g., when the UE does not perform UL transmission based on the UE-initiated COT at the beginning of the corresponding FFP-u), if the configured UL transmission (resources) are configured within a specific FFP-g period (without overlapping with an idle period of the corresponding FFP-g), and if the UE determines that a BS-initiated COT has been generated for the corresponding FFP-g (e.g., if the UE detects a DL signal based on the BS-initiated COT in the corresponding FFP-g), the UE may be configured to transmit the configured UL resources using a shared COT based on the BS-initiated COT (for convenience, this is defined as "Case 2").

[0416] C. Otherwise, if neither Case 1 nor Case 2 applies, the UE may be configured to drop the configured UL transmission.

[0417] 2) When a specific configured UL transmission (or multiple UL resources thereof) starts at the start of a specific FFP-u period (that is, the specific configured UL transmission is aligned with the start of the corresponding FFP-u) and the specific configured UL transmission (or a specific resource among the multiple UL resources) is configured to overlap with an idle period of FFP-u, the following UE operation may be considered.

[0418] A. If the configured UL transmission (or its multiple UL resources) starts within a specific FFP-g period and the configured UL transmission (or all multiple UL resources) does not overlap with the idle period related to FFP-g, and if the UE determines that a BS-initiated COT has been created for the corresponding FFP-g (for example, if the UE detects a DL signal based on the BS-initiated COT in the corresponding FFP-g), the UE may be configured to transmit the configured UL resources using a shared COT based on the BS-initiated COT (for convenience, this is defined as "Case 1").

[0419] B. Otherwise, if the configured UL transmission (or a plurality of UL resources thereof) starts within a specific FFP-g period and the configured UL transmission (or a specific resource among the plurality of UL resources) overlaps with an idle period related to the FFP-g, and if the UE determines that a BS-initiated COT has been created for the corresponding FFP-g (for example, if the UE detects a DL signal based on the BS-initiated COT in the corresponding FFP-g), the UE may be configured to drop transmission on the specific resource among the configured UL resources that overlaps with the idle period and perform transmission only on the remaining resources (which do not overlap with the idle period) using a shared COT based on the BS-initiated COT (for convenience, this is defined as "Case 2").

[0420] C. Otherwise, if neither Case 1 nor Case 2 applies, the UE may be configured to discard transmission on specific resources among the configured UL resources that overlap with the idle period associated with the FFP-u and perform transmission based on the UE-initiated COT only on the remaining resources (which do not overlap with the idle period) by creating 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 corresponding FFP-u).

[0421] [7]UE operation for UL transmission related to RACH procedure in FBE operation scenario

[0422] 1) Problematic situations

[0423] A. In FBE operation scenarios (e.g., for semi-static channel occupancy), transmission based on UE-initiated COT and the FFP-u parameter (e.g., period, offset, etc.) configuration for it (e.g., ue-SemiStaticChannelAccessConfig) may be supported / provided only for RRC connected mode UEs. For idle / inactive mode UEs, transmission based only on BS-initiated COT may be allowed based on FFP-g parameter configuration (by sharing FFP-g starting with BS-initiated COT).

[0424] B. In RRC connected mode, the UE may perform the above-mentioned CBRA or CFRA-related UL transmissions (e.g., PRACH transmission and / or Msg3 PUSCH transmission) for the following purposes: timing advance (TA) adjustment, scheduling request (SR) transmission, beam failure report (BFR) transmission, etc.

[0425] C. In the above RACH scenario, since the PRACH resources or Msg3 PUSCH resources transmitted by the RRC connected mode UE are UE-common UL resources configured for the idle / inactive mode UE (the corresponding UE also attempts to transmit), it is necessary to consider not only whether UE-initiated COT-based transmission is allowed on the corresponding UL resources but also the conditions for allowing UE-initiated COT-based transmission if allowed.

[0426] D. Specifically, until Rel.16 NR, UL transmission was allowed only in such a way that the UE shared FFP-g starting with BS-initiated COT. However, starting from Rel.17 NR, UE-initiated COT / FFP-u can also be supported. Assuming that in Rel.17 NR, UE-initiated COT / FFP-u is supported only for RRC connected mode UEs other than RRC inactive / idle mode UEs, in Rel.17, UL transmission can be allowed for RRC inactive / idle mode UEs only when FFP-g starting with BS-initiated COT is shared as in Rel.16 NR. Under this assumption, comparing the operation of the BS in Rel.16 NR and Rel.17 NR, if the Rel.16 NR BS does not generate FFP-g on the RACH resources (in other words, if the Rel.16 NR BS does not initiate BS-initiated channel occupation), the UE may not be allowed to perform UL transmission based on COT sharing. Therefore, the process for detecting UL transmissions from Rel.16 UEs based on COT sharing on the corresponding RACH resources can be omitted. For example, if a Rel.16 NR BS does not start channel occupation in an FFP-g period including RACH resources, the BS can assume that there are no UL transmissions based on COT sharing in the corresponding FFP-g (that is, there are no UL transmissions from all UEs up to Rel.16, including UL transmissions for RACH). Depending on the implementation, the BS can be configured to discard the UL reception process in the corresponding FFP-g period. If the BS operation is implemented as described above, it does not violate the NR specification protocol up to Rel.16. On the other hand, the Rel.17 NR BS should be able to receive not only UL transmissions based on COT sharing, but also UL transmissions performed by RRC connected mode UEs based on UE-initiated COT / FFP-u. For example, the Rel.17NR BS may consider that even if the Rel.17NR BS does not start channel occupation in the FFP-g period (including RACH resources), there may be UL transmissions performed by the RRC connected mode UE based on the UE-initiated COT / FFP-u. In other words, the Rel.17NR BS may not be able to confirm that there may be no UL transmissions in the entire FFP-g period based solely on the fact that the Rel.17NR BS does not start channel occupation in the corresponding FFP-g period.

[0427] 2) Proposal 1

[0428] A. When a (RRC connected mode) UE is configured with FFP-u parameters (e.g., higher layer parameter ue-SemiStaticChannelAccessConfig), the UE may perform UE-initiated COT-based transmissions (and BS-initiated COT-based transmissions (based on COT sharing)) in the corresponding FFP-u for RACH-related UL transmissions (e.g., PRACH, RAR grant-based (Msg3) PUSCH, HARQ-ACK PUCCH associated with MsgA and / or MsgB in a 2-step RACH procedure, etc.).

[0429] i. PRACH resources, (Msg3) PUSCH resources (related to RAR grants), MsgA resources, and / or HARQ-ACK PUCCH resources (related to MsgB) in which UE-initiated COT-based transmissions are allowed can be configured only when specific conditions are met. For example, the specific condition may be that the PRACH resources, (Msg3) PUSCH resources (related to RAR grants), MsgA resources, and / or HARQ-ACK PUCCH resources (related to MsgB) are aligned at the start of the FFP-u period (with the start timing / symbol of the signal).

[0430] 1. In this case, even if UE-initiated COT-based transmission is enabled / permitted, information about the COT initiator (e.g., UE-initiated COT or BS-initiated COT) may not be indicated by the MAC CE indicating the RAR grant (and / or DCI for scheduling retransmission) and / or HARQ-ACK PUCCH resources (related to MsgB) for scheduling (Msg3) PUSCH.

[0431] 2. For PRACH resources, (Msg3) PUSCH resources, MsgA resources and / or HARQ-ACK PUCCH resources (related to MsgB) that do not meet specific conditions, transmission based only on BS-initiated COT (based on COT sharing) may be allowed.

[0432] ii. As another example, the gNB (i.e., BS) may directly configure, to the UE, (the location of) PRACH resources, (Msg3) PUSCH resources (related to RAR grant), MsgA resources, and / or HARQ-ACK PUCCH resources (related to MsgB) in which UE-initiated COT-based transmission is enabled / permitted.

[0433] 1. In this case, even if UE-initiated COT-based transmission is enabled / permitted, information about the COT initiator (e.g., UE-initiated COT or BS-initiated COT) may not be indicated by the MAC CE indicating the RAR grant (and / or DCI for scheduling retransmission) and / or HARQ-ACK PUCCH resources (related to MsgB) for scheduling (Msg3) PUSCH.

[0434] 2. For PRACH resources, (Msg3) PUSCH resources, MsgA resources and / or HARQ-ACK PUCCH resources (related to MsgB) not included in the gNB (BS) configuration, transmission based only on BS-initiated COT (based on COT sharing) may be allowed.

[0435] iii. As another example, (UE-specific) PRACH resources, (Msg3) PUSCH resources (related to RAR grant), MsgA resources and / or HARQ-ACK PUCCH resources (related to MsgB) configured / indicated for CF-RACH (and / or BFR-RACH) (which is triggered via PDCCH command) may enable / allow transmission based on UE-initiated COT.

[0436] 1. In this case, information about the COT initiator (e.g., UE-initiated COT or BS-initiated COT) can be indicated by a MAC CE indicating the RAR grant (and / or DCI for scheduling retransmission) and / or HARQ-ACK PUCCH resources (related to MsgB) used to schedule (Msg3) PUSCH through the COT initiator (e.g., UE-initiated COT or BS-initiated COT information can be indicated).

[0437] 2. For resources related to RACH procedures other than the above CF-RACH (and / or BFR-RACH) (e.g., PRACH resources, (Msg3) PUSCH resources, MsgA resources, and / or HARQ-ACK PUCCH resources (related to MsgB)), only BS-initiated COT transmission (COT-based sharing) may be allowed. For example, even if a UE is configured with UE-initiated COT transmission and receives FFP-u parameter configuration (e.g., period, offset, etc.) for it (e.g., ue-SemiStaticChannelAccessConfig) and the UE is in RRC connected mode, if the corresponding resources are related to the CB-RACH procedure, only UL transmission of FFP-g starting with the BS-initiated COT may be shared, and UL transmission based on the UE-initiated COT (or UL transmission based on FFP-u starting with the UE-initiated COT) may not be allowed. Whether the corresponding resources are related to the CB-RACH procedure may be determined based on the initiation (or triggering) of the CB-RACH procedure. For example, the time resources included in the time period from when the CB-RACH procedure is started (or triggered) until the end of the CB-RACH procedure may be associated with the CB-RACH procedure. For example, if a first time period from the initiation (or triggering) of the CB-RACH procedure to the end of the CB-RACH procedure overlaps (at least partially) with a second time period associated with a specific FFP-u based on an FFP-u configuration (e.g., ue-SemiStaticChannelAccessConfig) received by the UE, then the (at least partially) overlapping resources may be associated with the CB-RACH procedure. Sharing of only UL transmissions of FFP-g starting with a BS-initiated COT may be allowed on resources overlapping with the first time period among the time resources included in the second time period, and UL transmissions based on a UE-initiated COT (or UL transmissions based on FFP-u starting with a UE-initiated COT) may not be allowed for the UE. Meanwhile, from the perspective of the UE, the first time period for the CB-RACH procedure may begin based on the CB-RACH procedure being determined / indicated. For example, the first time period for the CB-RACH procedure may be started based on the CB-RACH being triggered by the UE MAC layer or receiving a PDCCH order indicating the CB-RACH (even before the physical transmission of the CB-RACH preamble). The UE may not desire to perform UL transmission based on the UE-initiated COT (or UL transmission based on FFP-u started with the UE-initiated COT) during the CB-RACH procedure (i.e., during the first time period for the CB-RACH procedure).

[0438] For example, reference Figure 22While performing the CBRA procedure, the UE may perform UL transmissions based solely on COT sharing (e.g., UL transmissions including UL transmissions related to the CBRA procedure) for FFP-g#1 (regardless of whether the UE is in RRC connected mode or RRC inactive / idle mode). That is, the UE may not be allowed to initiate UE-initiated COT or perform UL transmissions based on UE-initiated COT in FFP-u#2. Since the start of FFP-u#3 overlaps with the CBRA procedure, UE-initiated channel occupation may not be allowed for the UE at the start of FFP-u#3. Therefore, the UE may not perform UL transmissions associated with UE-initiated channel occupation throughout FFP-u#3, which is only available when it starts with UE-initiated channel occupation. That is, during FFP-u#3, the UE may perform UL transmissions based solely on COT sharing for FFP-g#2. For FFP-u#3 after FFP-u#3, UL transmissions associated with UE-initiated channel occupation may be allowed. During the entire FFP-u#3 period, including timing t2 at the end of the CBRA procedure, UL transmission associated with UE-initiated channel occupation may not be allowed. During FFP-u#1, including timing t1 at the start of the CBRA procedure, the UE may not perform UL transmission associated with UE-initiated channel occupation after timing t1, but the UE may perform transmission based only on COT sharing for FFP-g#1. For example, even if the UE succeeds in UE-initiated channel occupation at the start of FFP-u#1, the UE may not be allowed to maintain UE-initiated channel occupation until after timing t1 at the start of the CBRA procedure within FFP-u#1.

[0439] For example, reference Figure 23, when the UE is not in RRC connected mode (No in A05), the UE needs to attempt channel access by sharing FFP-g starting with BS-initiated COT. When sharing COT is allowed, the UE can perform UL transmission (A30). When the UE is in RRC connected mode (Yes in A05), the UE can perform the channel access procedure for UL transmission depending on whether the UE receives the channel access configuration related to the UE-initiated COT (A10). When the UE does not have the capability for UE-initiated COT or does not receive the channel connection configuration related to the UE-initiated COT (No in A10), the UE can attempt channel access by sharing FFP-g starting with BS-initiated COT (A30). When the UE is configured with channel access based on UE-initiated COT (Yes in A10), if the corresponding UL transmission is related to the UE-initiated COT, it can be considered whether the UL transmission is used for the CBRA procedure (A15). When the corresponding UL transmission associated with the UE-initiated COT is for a CBRA procedure (Yes in A15) (e.g., when the corresponding FFP-u is an FFP-u for a CBRA procedure), even if the UE is configured for UE-initiated COT-based channel access (Yes in A10), the UE needs to attempt channel access by sharing the FFP-g that begins with the BS-initiated COT, rather than performing UE-initiated COT-based channel access. If the corresponding UL transmission is not for CBRA (No in A15), the UE may attempt UE-initiated COT-based channel access (A25 and A35). Specifically, the UE may determine, through channel sensing, whether it is capable of initiating UE-initiated channel occupation in the corresponding FFP-u (A25). If, through channel sensing, it is determined that the UE is unable to initiate UE-initiated channel occupation in the corresponding FFP-u (No in A25), the UE may attempt channel access by sharing the FFP-g that begins with the BS-initiated COT (A30). When it is determined through channel sensing that the UE is capable of initiating UE-initiated channel occupation in the corresponding FFP-u (yes in A25 ), the UE may perform channel access in the FFP-u starting with UE-initiated COT ( A35 ).

[0440] In the above example, UE-initiated COT-based UL transmission in FFP-u for CBRA may not be performed based on UE-initiated channel occupancy, but UE-initiated COT-based UL transmission in FFP-u for CFRA may be performed based on UE-initiated channel occupancy (e.g., no in A15 and A20, yes in A25 and A35). As described above in "1) Problematic Scenario," when a Rel.16 NR BS does not initiate channel occupancy during an FFP-g period that includes RACH resources, the BS may assume that there is no COT-shared UL transmission during the corresponding FFP-g period (that is, no UL transmission from all UEs prior to Rel.16, including UL transmission for RACH). Depending on the implementation, the BS may be configured to omit the UL reception process during the corresponding FFP-g period. If the above BS assumption can be effectively applied to a Rel.17 BS during CBRA, the complexity and power of the BS can be reduced. When a RACH resource is associated with CFRA, if the BS indicates a dedicated RACH preamble for CFRA to the UE, the BS may expect to receive the dedicated RACH preamble. Specifically, the BS needs to receive at least the dedicated RACH preamble in the UL (regardless of whether the UE FFP-u is generated), and therefore, the BS may not skip the UL reception process on the corresponding time resource. When a RACH resource is associated with CBRA, if there is a restriction that does not allow UE-initiated COT during CBRA and if the BS does not start channel occupation in the FFP-g period that includes the RACH resource as in the above example, the BS may assume that there is no UL transmission based on UE-initiated COT and / or COT sharing during the corresponding FFP-g period. Depending on the implementation, the BS may be configured to skip the UL reception process during the corresponding FFP-g period.

[0441] A. In this case, information about the COT initiator (e.g., whether it is UE-initiated COT or BS-initiated COT) may not be indicated by the MAC CE indicating the RAR grant (and / or DCI for scheduling retransmission) and / or HARQ-ACK PUCCH resources (related to MsgB) for scheduling (Msg3) PUSCH (or the COT initiator may always be defined / assumed to be BS-initiated COT).

[0442] B. As described above, even if the UE is allowed to perform UE-initiated COT transmission on (specific) RACH-related PRACH resources, (Msg3) PUSCH resources, MsgA resources and / or HARQ-ACK PUCCH resources (related to MsgB) (or even if the UE is configured with FFP-u parameters), the PRACH resources, (Msg3) PUSCH resources, MsgA resources and / or HARQ-ACK PUCCH resources (related to MsgB) that overlap with the idle period related to FFP-g may always be regarded as invalid resources (regardless of whether the UE creates a UE-initiated COT), and therefore transmission may not be enabled / allowed.

[0443] 3) Proposal 2

[0444] A. Even if the (RRC connected mode) UE is configured with FFP-u parameters, the UE may be allowed to perform transmission based only on the BS-initiated COT (based on COT sharing) for all RACH-related UL transmissions (e.g., PRACH, RAR grant-based (Msg3) PUSCH, HARQ-ACK PUCCH related to MsgA and / or MsgB in a 2-step RACH procedure, etc.) (in a state where the UE ignores the configured FFP-u for the corresponding resources (i.e., the UE discards transmission based on the UE-initiated COT)).

[0445] i. In this case, for the (UE-dedicated) PRACH resources, (Msg3) PUSCH resources (related to RAR grant), MsgA resources and / or HARQ-ACK PUCCH resources (related to MsgB) configured / indicated for CF-RACH (and / or BFR-RACH) (which is triggered via PDCCH order), the UE can be configured to attempt transmission based only on BS-initiated COT (based on COT sharing) for the corresponding resources while ignoring the configured FFP-u (or discarding transmission based on UE-initiated COT).

[0446] ii. In this case, information about the COT initiator (e.g., whether it is UE-initiated COT or BS-initiated COT) may not be indicated by the MAC CE indicating the RAR grant (and / or DCI for scheduling retransmission) and / or HARQ-ACK PUCCH resources (related to MsgB) for scheduling (Msg3) PUSCH (or the COT initiator may always be defined / assumed to be BS-initiated COT).

[0447] 1. In this case, even for (UE-specific) PRACH resources and / or HARQ-ACK PUCCH resources (related to MsgB) configured / indicated for CF-RACH (and / or BFR-RACH) (which is triggered via PDCCH order), the UE can be configured to assume BS-initiated COT-based transmission without indicating information about the COT initiator through the MAC CE indicating the RAR grant (and / or DCI for scheduling retransmission) and / or HARQ-ACK PUCCH resources (corresponding to MsgB) for scheduling the corresponding (Msg3) PUSCH.

[0448] B. Even if the UE is configured with the FFP-u parameters as described above, PRACH resources, (Msg3) PUSCH resources, MsgA resources and / or HARQ-ACK PUCCH resources (related to MsgB) that overlap with idle periods related to FFP-g may always be regarded as invalid resources (regardless of whether the UE creates a UE-initiated COT), and therefore no transmission is enabled / allowed.

[0449] Figure 24 2 is a diagram for explaining operation of a UE on a shared spectrum in a wireless communication system according to one embodiment of the present disclosure. Figure 24 The exemplary application method of the above proposal is shown, and the scope of the present disclosure is not limited to Figure 24 In addition, in order to understand Figure 24 For the embodiments, please refer to the above content.

[0450] refer to Figure 24 , the UE can receive configuration information for channel access based on UE-initiated channel occupancy.

[0451] The UE may determine whether UL transmission associated with the UE-initiated channel occupancy is allowed during the first time period based on the configuration information ( B10 ).

[0452] The UE may access the channel based on the determined result (B15).

[0453] Based on the fact that resources used for UL transmission associated with UE-initiated channel occupancy in the first time period are related to the random access procedure, and the random access procedure is a contention-based random access procedure, the UE may determine that UL transmission associated with UE-initiated channel occupancy is not allowed in the first time period.

[0454] Based on the random access procedure being a contention-based random access procedure, the UE may determine that UL transmission associated with UE-initiated channel occupancy is not allowed during the random access procedure.

[0455] Based on determining that UL transmission associated with the UE-initiated channel occupancy is not allowed, the UE may perform UL transmission by accessing the channel in a second period starting with the BS-initiated channel occupancy based on COT sharing.

[0456] While the UE is in RRC inactive mode or RRC idle mode, UL transmission associated with UE-initiated channel occupation may not be allowed.

[0457] Based on the UE being in RRC connected mode and the random access procedure not being a contention-based random access procedure, the UE may determine that UL transmission associated with the UE-initiated channel occupation is allowed in the first time period based on the configuration information.

[0458] Based on the UE being in RRC connected mode, but resources used for UL transmission associated with UE-initiated channel occupation in the first period are related to a contention-based random access procedure, the UE may determine that UL transmission associated with UE-initiated channel occupation is not allowed in the first period.

[0459] The UL transmission may include UL transmission related to a random access procedure.

[0460] The UE may determine that UL transmissions associated with UE-initiated channel occupancy are not allowed for the following: physical random access channel (PRACH) resources, physical uplink shared channel (PUSCH) resources for message 3 (Msg3), message A (MsgA) resources including a PRACH preamble in a 2-step random access, or physical uplink control channel (PUCCH) resources carrying a hybrid automatic repeat request acknowledgement (HARQ-ACK) for message B (MsgB) as a response to MsgA, which is associated with a contention-based random access procedure.

[0461] The random access procedure can be used for TA adjustment, SR or BFR in the RRC connected state.

[0462] Figure 25 is a diagram for explaining an operation of a BS on a shared spectrum in a wireless communication system according to an embodiment of the present disclosure. Figure 25 The exemplary application method of the above proposal is shown, and the scope of the present disclosure is not limited to Figure 25 In addition, in order to understand Figure 25 For the embodiments, please refer to the above content.

[0463] refer to Figure 25 , the BS may transmit configuration information (C05) for channel access based on the channel occupancy initiated by the UE.

[0464] The BS may determine whether to allow UL transmission associated with the UE-initiated channel occupancy in the first period based on the configuration information ( C10 ).

[0465] The BS may receive a UL signal based on the determined result ( C15 ).

[0466] Based on the fact that resources used for UL transmission associated with UE-initiated channel occupancy in the first time period are related to the random access procedure, and the random access procedure is a contention-based random access procedure, the BS may determine that UL transmission associated with UE-initiated channel occupancy is not allowed in the first time period.

[0467] Based on determining that UL transmission associated with UE-initiated channel occupancy is not allowed in the first time period, a UL signal may be received in a second time period starting with BS-initiated channel occupancy based on COT sharing.

[0468] Based on the fact that the random access procedure is a contention-based random access procedure, the BS may determine that UL transmission associated with the UE-initiated channel occupancy is not allowed during the random access procedure.

[0469] Based on determining that UL transmission associated with the UE-initiated channel occupancy is not allowed, the BS may receive a UL signal transmitted in a second period starting with the BS-initiated channel occupancy based on COT sharing.

[0470] While the UE is in RRC inactive mode or RRC idle mode, UL transmission associated with UE-initiated channel occupation may not be allowed.

[0471] Based on the UE being in the RRC connected mode and the random access procedure not being a contention-based random access procedure, the BS may determine to allow UL transmission associated with the channel occupancy initiated by the UE in the first period based on the configuration information.

[0472] Based on the UE being in RRC connected mode, but resources used for UL transmission associated with UE-initiated channel occupancy in the first period are related to a contention-based random access procedure, the BS may determine that UL transmission associated with UE-initiated channel occupancy is not allowed in the first period.

[0473] The UL signal may include a UL signal related to a random access procedure.

[0474] The BS may determine that UL transmission associated with UE-initiated channel occupancy is not allowed for the following: physical random access channel (PRACH) resources, physical uplink shared channel (PUSCH) resources for message 3 (Msg3), message A (MsgA) resources including a PRACH preamble in a 2-step random access, or physical uplink control channel (PUCCH) resources carrying a hybrid automatic repeat request acknowledgement (HARQ-ACK) for message B (MsgB) as a response to MsgA, which is associated with a contention-based random access procedure.

[0475] The random access procedure can be used for TA adjustment, SR or BFR in the RRC connected state.

[0476] Figure 26 A communication system 1 applied to the present disclosure is shown.

[0477] refer to Figure 26 , a communication system 1 applied to the present disclosure includes a wireless device, a base station (BS), and a network. Herein, a wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G New RAT (NR) or Long Term Evolution (LTE)), and may be referred to as a communication / radio / 5G device. The wireless device may include, but is not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and may be implemented in the form of head-mounted devices (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, and the like. Handheld devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node relative to other wireless devices.

[0478] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can perform direct communication (e.g., sidelink communication) with each other without going through the BS / network. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0479] Wireless communication / connections 150a, 150b, or 150c may be established between wireless devices 100a to 100f / BS 200 or BS 200 / BS 200. Here, wireless communication / connections may be established via various RATs (e.g., 5G NR), such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device may transmit / receive radio signals to / from each other via the wireless communication / connections 150a and 150b. For example, the wireless communication / connections 150a and 150b may transmit / receive signals via various physical channels. To this end, at least a portion of various configuration information for configuring processes for transmitting / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes may be performed based on various proposals of the present disclosure.

[0480] Figure 27 A wireless device suitable for use with the present disclosure is shown.

[0481] refer to Figure 27 , the first wireless device 100 and the second wireless device 200 can transmit radio signals via various RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to Figure 26 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

[0482] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor 102 may process information within the memory 104 to generate first information / signals, and then transmit a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including commands for executing some or all of the processes controlled by the processor 102 or for executing the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed herein. Herein, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0483] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor 202 may process information within the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals through the transceiver 206, and then store information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including commands for executing some or all of the processes controlled by the processor 202 or for executing the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed herein. Herein, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0484] Hereinafter, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document, and provide the generated signal to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.

[0485] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, 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) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented in the form of codes, commands and / or command sets using firmware or software.

[0486] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 may be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies, such as wired or wireless connections.

[0487] One or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels mentioned in the methods and / or operational flow charts of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 may execute control so that one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may execute control so that one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc. from RF band signals to baseband signals so that the received user data, control information, radio signals / channels, etc. may be processed using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0488] Figure 28 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be used according to the usage / service (refer to Figure 26 ) are implemented in various forms.

[0489] refer to Figure 28 , wireless devices 100 and 200 may correspond to Figure 27The wireless devices 100 and 200 may be configured by various elements, components, units / portions and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Figure 27 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Figure 27 The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. The control unit 120 may transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 via a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 via the wireless / wired interface in the memory unit 130.

[0490] The additional components 140 may be configured differently depending on the type of wireless device. For example, the additional components 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in the following manner: Figure 26 100a), vehicles ( Figure 26 100b-1 and 100b-2), XR devices ( Figure 26 100c), handheld devices ( Figure 26 100d), household appliances ( Figure 26 100e), IoT devices ( Figure 26 100f), digital broadcasting terminals, holographic equipment, public safety equipment, MTC equipment, medical equipment, financial technology equipment (or financial equipment), security equipment, climate / environmental equipment, AI servers / equipment ( Figure 26 400), BS( Figure 26 200), network nodes, etc. The wireless device can be used in a mobile or fixed location depending on the use case / service.

[0491] exist Figure 28In the present disclosure, the various elements, components, units / portions, and / or modules in wireless devices 100 and 200 may all be connected to each other via a wired interface, or at least a portion thereof may be wirelessly connected via communication unit 110. For example, in each of wireless devices 100 and 200, control unit 120 and communication unit 110 may be wired, and control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected via communication unit 110. The various elements, components, units / portions, and / or modules within wireless devices 100 and 200 may also include one or more elements. For example, control unit 120 may be configured by a collection of one or more processors. As an example, control unit 120 may be configured by a collection of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, memory 130 may be configured by random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0492] Figure 29 A vehicle or autonomous driving vehicle applicable to the present disclosure is shown. The vehicle or autonomous driving vehicle can be implemented by a mobile robot, a car, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.

[0493] refer to Figure 29 , the vehicle or autonomous driving vehicle 100 may include 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 may be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to Figure 28 Blocks 110 / 130 / 140.

[0494] The communication unit 110 can send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, base stations (e.g., gNBs and roadside units), and servers. The control unit 120 can perform various operations by controlling components of the vehicle or autonomous vehicle 100. The control unit 120 may include an electronic control unit (ECU). The drive unit 140a can enable the vehicle or autonomous vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a power system, wheels, brakes, a steering system, etc. The power supply unit 140b can supply power to the vehicle or autonomous vehicle 100 and may include wired / wireless charging circuits, a battery, etc. The sensor unit 140c can acquire vehicle status, surrounding environment information, user information, etc. The sensor unit 140 c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a location module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a depth sensor, an ultrasonic sensor, a lighting sensor, a pedal position sensor, etc. The autonomous driving unit 140 d may implement a technology for maintaining a lane in which the vehicle is traveling, a technology for automatically adjusting the speed (e.g., adaptive cruise control), a technology for autonomously traveling along a determined path, a technology for traveling by automatically setting a path if a destination is set, etc.

[0495] For example, the communication unit 110 may receive map data, traffic information data, and the like from an external server. The autonomous driving unit 140d may generate an autonomous driving path and driving plan based on the obtained data. The control unit 120 may control the drive unit 140a so that the vehicle or autonomous driving vehicle 100 moves along the autonomous driving path according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit 110 may aperiodically or periodically obtain recent traffic information data from the external server and obtain surrounding traffic information data from neighboring vehicles. During autonomous driving, the sensor unit 140c may obtain vehicle status and / or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving path and driving plan based on the newly obtained data / information. The communication unit 110 may transmit information regarding the vehicle's location, autonomous driving path, and / or driving plan to the external server. The external server may predict traffic information data based on information collected from the vehicle or autonomous driving vehicle using AI technology, etc., and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0496] Figure 30 is a diagram illustrating a DRX operation of a UE according to an embodiment of the present disclosure.

[0497] The UE may perform DRX operations in the procedures and / or methods described / proposed above. A UE configured with DRX can reduce power consumption by discontinuously receiving downlink signals. DRX may be performed in the RRC_IDLE state, the RRC_INACTIVE state, and the RRC_CONNECTED state. The UE performs DRX in the RRC_IDLE state and the RRC_INACTIVE state to discontinuously receive paging signals. DRX in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described below.

[0498] refer to Figure 30 , the DRX cycle includes an on-duration and a DRX opportunity. The DRX cycle defines the time interval between periodic repetitions of the on-duration. The on-duration is the time period during which the UE monitors the PDCCH. When the UE is configured with DRX, the UE performs PDCCH monitoring during the on-duration. When the UE successfully detects the PDCCH during the PDCCH monitoring period, the UE starts the inactivity timer and remains awake. Conversely, when the UE fails to detect any PDCCH during the PDCCH monitoring period, the UE transitions to a sleep state after the on-duration. Therefore, when DRX is configured, PDCCH monitoring / reception may be performed discontinuously in the time domain in the processes and / or methods described / proposed above. For example, when DRX is configured, the PDCCH reception timing (e.g., a time slot with a PDCCH SS) may be configured discontinuously according to the DRX configuration in the present disclosure. Conversely, when DRX is not configured, PDCCH monitoring / reception may be performed continuously in the time domain. For example, when DRX is not configured, the PDCCH reception timing (e.g., a time slot with a PDCCH SS) may be configured continuously in the present disclosure. Regardless of whether DRX is configured, PDCCH monitoring may be restricted during time periods configured as measurement gaps.

[0499] Table 9 describes the DRX operation of the UE (in the RRC_CONNECTED state). Referring to Table 9, DRX configuration information is received through high-layer signaling (e.g., RRC signaling), and DRX on / off is controlled by a DRX command from the MAC layer. Once DRX is configured, the UE may discontinuously perform PDCCH monitoring while executing the procedures and / or methods described / proposed above, such as Figure 5 shown.

[0500] [Table 9]

[0501]

[0502] MAC-CellGroupConfig includes the configuration information required to configure MAC parameters for the cell group. MAC-CellGroupConfig may also include DRX configuration information. For example, when defining DRX, MAC-CellGroupConfig may include the following information.

[0503] -drx-OnDurationTimer value: defines the duration of the start period of the DRX cycle.

[0504] - Value of drx-InactivityTimer: defines the duration of the time period that the UE wakes up after detecting a PDCCH opportunity indicating a PDCCH for initial UL or DL ​​data.

[0505] -drx-HARQ-RTT-TimerDL value: defines the duration of the maximum time period after receiving a DL initial transmission until a DL retransmission is received.

[0506] -drx-HARQ-RTT-TimerDL value: defines the duration of the maximum time period after receiving a UL initial transmission grant until receiving a UL retransmission grant.

[0507] -drx-LongCycleStartOffset: defines the duration and start time of the DRX cycle.

[0508] -drx-ShortCycle (optional): defines the duration of the short DRX cycle.

[0509] When any of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerDL is running, the UE performs PDCCH monitoring at each PDCCH opportunity and remains in the awake state.

[0510] The above-mentioned embodiments correspond to the combination of elements and features of the present disclosure in a prescribed form. Furthermore, unless each element or feature is explicitly mentioned, each element or feature can be considered to be selective. Each of the elements or features can be implemented in a form that cannot be combined with other elements or features. In addition, by partially combining elements and / or features together, it is possible to implement the embodiments of the present disclosure. The operation sequence explained for each embodiment of the present disclosure can be modified. Some configurations or features of an embodiment can be included in another embodiment, or can replace the corresponding configuration or features of another embodiment. Furthermore, it is clearly understood that the embodiments are configured by combining claims that do not have an explicit reference relationship in the attached claims, or can be included as new claims obtained by amendment after submitting the application.

[0511] Those skilled in the art will understand that the present disclosure can be implemented in other specific ways than those set forth herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above embodiments are to be construed in all respects as illustrative and not restrictive. The scope of the present disclosure is to be determined by the appended claims and their legal equivalents, not by the above description, and all changes coming within the meaning and equivalent range of the appended claims are intended to be embraced therein.

[0512] As is apparent from the above description, the present disclosure has the following effects.

[0513] According to the present disclosure, wireless signal transmission and reception can be efficiently performed in a wireless communication system.

[0514] It will be apparent to those skilled in the art that various modifications and variations can be made in the present disclosure without departing from the spirit and scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure as long as they fall within the scope of the appended claims and their equivalents.

Claims

1. A method for performing a channel access procedure on a shared spectrum by a user equipment (UE) in a wireless communication system, the method comprising: receiving configuration information for channel access based on UE-initiated channel occupancy; determining whether uplink (UL) transmission associated with the UE-initiated channel occupation is allowed during a first time period based on the configuration information; as well as accessing a channel based on a result of said determining, Wherein, based on the fact that the resources used for the UL transmission associated with the channel occupancy initiated by the UE in the first time period are related to a random access procedure, and the random access procedure is a contention-based random access procedure, the UE determines that the UL transmission associated with the channel occupancy initiated by the UE is not allowed in the first time period.

2. The method according to claim 1, wherein Based on the random access procedure being the contention-based random access procedure, the UE determines that the UL transmission associated with the UE-initiated channel occupancy is not allowed during the random access procedure.

3. The method according to claim 1, wherein Based on determining that the UL transmission associated with the UE-initiated channel occupancy is not allowed, the UE performs the UL transmission by accessing the channel in a second period starting with base station-initiated (BS-initiated) channel occupancy shared based on channel occupancy time (COT).

4. The method according to claim 1, wherein While the UE is in a radio resource control (RRC) inactive mode or an RRC idle mode, the UL transmission associated with the UE-initiated channel occupation is not allowed.

5. The method according to claim 4, wherein Based on the UE being in RRC connected mode and the random access procedure not being the contention-based random access procedure, the UE determines to allow the UL transmission associated with the channel occupation initiated by the UE in the first time period based on the configuration information.

6. The method according to claim 4, wherein: Based on the UE being in the RRC connected mode, but the resources used for the UL transmission associated with the channel occupation initiated by the UE in the first time period are related to the contention-based random access procedure, the UE determines that the UL transmission associated with the channel occupation initiated by the UE is not allowed in the first time period.

7. The method according to claim 1, wherein The UL transmission includes UL transmission related to the random access procedure.

8. The method according to claim 1, wherein The UE determines that the UL transmission associated with the channel occupation initiated by the UE is not allowed for the following: physical random access channel (PRACH) resources, physical uplink shared channel (PUSCH) resources for message 3 (Msg3), message A (MsgA) resources including a PRACH preamble in a 2-step random access, or physical uplink control channel (PUCCH) resources carrying a hybrid automatic repeat request acknowledgement (HARQ-ACK) for message B (MsgB) as a response to MsgA, which is related to the contention-based random access procedure.

9. The method according to claim 1, wherein The random access procedure is used for timing advance (TA) adjustment, scheduling request (SR) or beam failure report (BFR) in the radio resource control (RRC) connected state. 10 . A computer-readable medium storing a program for executing the method according to claim 1 .

11. A user equipment (UE) configured to perform a channel access procedure on a shared spectrum in a wireless communication system, the UE comprising: transceiver; as well as a processor configured to: controlling the transceiver to receive configuration information for channel access based on UE-initiated channel occupancy; determining whether uplink (UL) transmission associated with the UE-initiated channel occupation is allowed during a first time period based on the configuration information; as well as accessing a channel based on a result of said determining, The processor determines that the UL transmission associated with the channel occupancy initiated by the UE is not allowed in the first time period based on that the resources used for the UL transmission associated with the channel occupancy initiated by the UE in the first time period are related to a random access procedure, and the random access procedure is a contention-based random access procedure.

12. A device configured to control a user equipment (UE) in a wireless communication system, the device comprising: a memory configured to store instructions; as well as a processor configured to execute the instructions to perform a channel access procedure on a shared spectrum, Wherein, the processor is configured to: receiving configuration information for channel access based on UE-initiated channel occupancy; determining whether uplink (UL) transmission associated with the UE-initiated channel occupancy is allowed during a first time period based on the configuration information; and accessing a channel based on a result of the determination, and The processor determines that the UL transmission associated with the channel occupancy initiated by the UE is not allowed in the first time period based on that the resources used for the UL transmission associated with the channel occupancy initiated by the UE in the first time period are related to a random access procedure, and the random access procedure is a contention-based random access procedure.

13. A method for receiving a signal from a user equipment (UE) on a shared spectrum by a base station (BS) in a wireless communication system, the method comprising: Sending configuration information for channel access based on UE-initiated channel occupancy; determining whether uplink (UL) transmission associated with the UE-initiated channel occupation is allowed during a first time period based on the configuration information; as well as receiving a UL signal based on a result of the determining, Wherein, based on the fact that the resources used for the UL transmission associated with the channel occupancy initiated by the UE in the first time period are related to a random access procedure, and the random access procedure is a contention-based random access procedure, the BS determines that the UL transmission associated with the channel occupancy initiated by the UE is not allowed in the first time period.

14. The method according to claim 13, wherein: Based on determining that the UL transmission associated with the UE-initiated channel occupancy is not allowed in the first time period, the UL signal is received in a second time period starting with BS-initiated channel occupancy based on channel occupancy time (COT) sharing.

15. A base station (BS) configured to receive a signal from a user equipment (UE) on a shared spectrum, the BS comprising: transceiver; as well as a processor configured to: controlling the transceiver to transmit configuration information for channel access based on UE-initiated channel occupancy; determining whether uplink (UL) transmission associated with the UE-initiated channel occupation is allowed during a first time period based on the configuration information; as well as receiving a UL signal based on a result of the determining, The processor determines that the UL transmission associated with the channel occupancy initiated by the UE is not allowed in the first time period based on that the resources used for the UL transmission associated with the channel occupancy initiated by the UE in the first time period are related to a random access procedure, and the random access procedure is a contention-based random access procedure.

Images