Method and device for sending and receiving wireless signals in wireless communication system

Abstract

According to an embodiment of the present disclosure, a UE can obtain information related to a fixed frame period (FFP) and perform a clear channel assessment (CCA) on at least one FFP starting with a UE-initiated channel occupancy time (COT) for uplink signal transmission, wherein the FFP-related information may include information about an FFP start offset and information about an FFP duration or period, and the UE can identify the start time of a corresponding FFP based on the FFP start offset having OFDM symbol-level granularity.

Description

Technical Field

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

[0002] In general, wireless communication systems are developing to cover a wide range in various ways to provide communication services such as audio communication services, data communication services, etc. 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, the multiple access system can 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

[0003] Technical issues

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

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

[0006] Technical Solutions

[0007] According to one aspect of the present disclosure, a method for performing a channel access procedure on a shared spectrum by a user equipment (UE) in a wireless communication system may include: obtaining fixed frame period (FFP) related information for a frame-based device (FBE); performing a clear channel assessment (CCA) on at least one FFP starting with a channel occupancy time (COT) initiated by the UE based on the FFP related information; and sending an uplink signal in the FFP determined based on the CCA. The FFP related information may include information about an FFP start offset and information about an FFP duration or period, and the UE may identify the start time of the FFP based on the FFP start offset having an orthogonal frequency division multiplexing (OFDM) symbol-level granularity.

[0008] The maximum value of the FFP start offset with OFDM symbol level granularity may be determined based on the length of the FFP duration or period.

[0009] The first time length indicated by the information about the FFP start offset may always be set to be smaller than the second time length indicated by the information about the FFP duration or period.

[0010] FFP related information may be obtained through higher layer signaling.

[0011] When the result of the CCA is busy and the UE cannot start the UE's COT in the FFP, the UE may transmit an uplink signal based on the COT initiated by the shared base station (BS).

[0012] At least one FFP started with a COT initiated by the UE may be a first type FFP, and the FFP started with a COT initiated by the BS may be a second type FFP different from the first type FFP. The start of the first type FFP may not be time-aligned with the start of the second type FFP. The start of the idle period included in the first type FFP may be time-aligned with the start of the idle period included in the second type FFP.

[0013] According to an aspect of the present disclosure, a computer-readable recording medium recording a program for executing the above-mentioned signal receiving method may be provided.

[0014] According to one aspect of the present disclosure, a UE for executing the above signal receiving method may be provided.

[0015] According to one aspect of the present disclosure, a device for controlling a UE to perform the above-mentioned signal receiving method may be provided.

[0016] According to one aspect of the present disclosure, a method for receiving a signal on a shared spectrum by a BS in a wireless communication system may include: sending FFP-related information for FBE; and monitoring an uplink signal in each FFP starting with a channel occupation time (COT) initiated by a UE based on the FFP-related information. The FFP-related information may include information about an FFP start offset and information about an FFP duration or cycle, and the BS may always set a first time length corresponding to the FFP start offset to be less than a second time length corresponding to the FFP duration or cycle, and indicate the determined first time length based on an orthogonal frequency division multiplexing (OFDM) symbol-level granularity through the information about the FFP start offset.

[0017] According to one aspect of the present disclosure, a BS for performing the above-mentioned signal transmission method may be provided.

[0018] Effects of the Invention

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

[0020] Those skilled in the art will appreciate that the effects that can be achieved using the present disclosure are not limited to the contents specifically described above, and other advantages of the present disclosure will be more clearly understood from the following detailed description in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0022] Figure 1 illustrates 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;

[0023] Figure 2 illustrates the radio frame structure;

[0024] Figure 3 A resource grid of illustrated time slots;

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

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

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

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

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

[0030] Fig. 9 An exemplary method of occupying resources in an unlicensed band is illustrated;

[0031] Fig.10 illustrates an exemplary frame-based equipment (FBE) based channel access;

[0032] Fig.11 illustrates an exemplary load-based equipment (LBE) based channel access;

[0033] Fig.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);

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

[0035] Fig.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;

[0036] Fig.15 is a diagram illustrating a channel access method according to an embodiment of the present disclosure;

[0037] Fig.16 is a diagram illustrating a fixed frame period (FFP) according to an embodiment of the present disclosure;

[0038] Fig.17 is a diagram illustrating FFP start offset and FFP duration according to an embodiment of the present disclosure;

[0039] Fig.18 is a diagram illustrating a signal flow for a frame-based equipment (FBE)-based channel access method on a shared spectrum according to an embodiment of the present disclosure;

[0040] Figures 19 to 22 is a diagram illustrating an exemplary communication system 1 and an exemplary wireless device applied to the present disclosure; and

[0041] Fig.23 is a diagram illustrating an exemplary discontinuous reception (DRX) operation applicable to the present disclosure. DETAILED DESCRIPTION

[0042] 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)), IEEE802.20, and Evolved UTRA (E-UTRA). UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a 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.

[0043] As more and more communication devices require greater communication capacity, enhanced mobile broadband communications relative to traditional radio access technologies (RATs) are needed. In addition, large-scale machine-type communications (MTC), which can provide various services anytime and anywhere by connecting multiple devices and objects, is another important issue to be considered for next-generation 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 communications (eMBB), massive MTC, and ultra-reliable low-latency communications (URLLC). In this disclosure, for simplicity, this technology will be referred to as NR (new radio or new RAT).

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

[0045] In the present disclosure, the term "set / setting" may be replaced with "configure / configuration", and the two may be used interchangeably. In addition, conditional expressions (e.g., "if", "in this case", or "when...") may be replaced with "based on" or "under the situation / state of...". In addition, the operation or software / hardware (SW / HW) configuration of the user equipment (UE) / base station (BS) may be derived / understood based on the satisfaction of the corresponding condition. When the process on the receiving (or transmitting) side can be derived / understood from the process on the transmitting (or receiving) side in the signal transmission / reception between the wireless communication device (e.g., BS and UE), its description may be omitted. For example, the signal determination / generation / encoding / transmission on the transmitting side may be understood as the signal monitoring reception / decoding / determination on the receiving side. In addition, when it is said that the UE performs (or does not perform) a specific operation, this may also be interpreted as the BS expecting / assuming (or not expecting / assuming) that the UE performs a specific operation. When it is said that the BS performs (or does not perform) a specific operation, this may also be interpreted as the UE expecting / assuming (or not expecting / assuming) that the BS performs a specific operation. In the following description, for the convenience of description, chapters, 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 each of them can only be implemented separately. Unless explicitly contradicted, it can be concluded / understood that at least some of the chapters, embodiments, examples, options, methods, schemes, etc. can be implemented in combination or can be omitted.

[0046] In a wireless communication system, a user equipment (UE) receives information from a base station (BS) through a downlink (DL) and transmits information to the BS through 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 according to the type / purpose of the information transmitted and received by the UE and the BS.

[0047] Figure 1 Illustration of physical channels used in a 3GPP NR system and a general signal transmission method using the same.

[0048] 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., establishes 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. The UE can receive a DL reference signal (RS) during the initial cell search process to monitor the DL channel status.

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

[0050] The UE may perform a random access procedure to access the BS in steps S103 to S106. For random access, the UE may send 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 perform a contention resolution procedure by further sending a PRACH (S105) and receiving a PDCCH and a PDSCH corresponding to the PDCCH (S106).

[0051] After the foregoing 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 confirmation / negative determination (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, UCI may be sent on PUSCH when control information and service data need to be sent simultaneously. In addition, UCI may be sent aperiodically via PUSCH according to the request / command of the network.

[0052] Figure 2 Figure 1. Radio frame structure. In NR, uplink transmission and downlink transmission are configured in frames. Each radio frame has a length of 10 ms and is divided into two 5 ms half frames (HF). Each half frame is divided into five 1 ms 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.

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

[0054] [Table 1]

[0055] <![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

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

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

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

[0059] 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 the SCS when the extended CP is used.

[0060] [Table 2]

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

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

[0063] In the NR system, OFDM parameter sets (e.g., SCS) 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) (referred to as a time unit (TU) for simplicity) consisting of the same number of symbols may be configured differently between aggregated cells. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).

[0064] Figure 3 A 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 (e.g., 12 consecutive subcarriers) in the frequency domain. A bandwidth part (BWP) may 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 may include up to N (e.g., five) BWPs. Data communication may be performed via enabled BWPs, and only one BWP may be enabled for a UE. In a resource grid, each element is referred to as a resource element (RE), and a complex symbol may be mapped to each RE.

[0065] Figure 4An exemplary mapping of physical channels in a time slot is illustrated. PDCCH may be sent in the DL control region, and PDSCH may be sent in the DL data region. PUCCH may be sent in the UL control region, and PUSCH may be sent in the UL data region. A guard period (GP) provides a time gap for a transmission mode to reception mode switch or a reception mode to transmission mode switch at a BS and a UE. Some symbols in a subframe at the time of a DL to UL switch may be configured as a GP.

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

[0067] 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 purpose of the PDCCH, the CRC is masked with various identifiers (IDs) (e.g., radio network temporary identifiers (RNTI)). For example, if the PDCCH is used 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).

[0068] The PDCCH includes 1, 2, 4, 8 or 16 control channel elements (CCEs) depending on its aggregation level (AL). CCE is a logical allocation unit for providing a specific code rate for the PDCCH according to the radio channel state. CCE includes 6 resource element groups (REGs), each REG is 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 the CORESET can be configured by higher layer signaling.

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

[0070] -controlResourceSetId: CORESET associated with SS.

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

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

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

[0074] * The timing (eg, time / frequency resource) at which the UE is to monitor a PDCCH candidate is defined as a PDCCH (monitoring) timing. One or more PDCCH (monitoring) timings may be configured in a time slot.

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

[0076] [Table 3]

[0077]

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

[0079] [Table 4]

[0080] DCI format use 0_0 PUSCH Scheduling in a Cell 0_1 PUSCH Scheduling in a Cell 1_0 Scheduling of PDSCH in a cell 1_1 Scheduling of 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 that the transmission is not intended for the UE 2_2 Transmission of TPC commands for PUCCH and PUSCH 2_3 Transmission of a set of TPC commands via SRS transmission of one or more UEs

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

[0082] 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 the fallback DCI format, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, the DCI size / field configuration varies in the non-fallback DCI format depending on the UE configuration.

[0083] 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 the basis of codewords, 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 a mapped layer with DMRS and sent through a corresponding antenna port.

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

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

[0086] -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. The HARQ-ACK response includes a positive ACK (abbreviated as ACK), a negative ACK (NACK), a discontinuous transmission (DTX), or NACK / DTX. The term HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

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

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

[0089] [Table 5]

[0090]

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

[0092] PUCCH format 1 transmits up to 2 bits of UCI in the time domain, and spreads the modulation symbol of UCI in the time domain using an orthogonal cover code (OCC) (which is configured differently depending on whether frequency hopping is performed). DMRS is transmitted with a symbol in which no modulation symbol is transmitted (ie, transmitted in time division multiplexing (TDM)).

[0093] PUCCH format 2 conveys more than 2 bits of UCI, and the modulation symbols of DCI are sent with DMRS in frequency division multiplexing (FDM). DMRS are located in symbols #1, #4, #7, and #10 of a given RB with a density of 1 / 3. Pseudo-noise (PN) sequences are used for DMRS sequences. For 2-symbol PUCCH format 2, frequency hopping can be activated.

[0094] PUCCH format 3 does not support UE multiplexing in the same PRBS and conveys UCI of more than 2 bits. In other words, the PUCCH resources of PUCCH format 3 do not include OCC. The modulation symbols and DMRS are transmitted in TDM.

[0095] PUCCH format 4 supports multiplexing of up to 4 UEs in the same PRBS and delivers more than 2 bits of UCI. In other words, the PUCCH resources of PUCCH format 3 include OCC. The modulation symbols and DMRS are transmitted in TDM.

[0096] The PUSCH delivers UL data (e.g., UL shared channel transport block (UL-SCH TB)) 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 by 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 a 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.

[0097] Figure 5 An exemplary ACK / NACK transmission process is shown. 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 K0 and the PDSCH-to-HARQ-ACK reporting offset K1. For example, DCI format 1_0 and DCI format 1_1 may include the following information.

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

[0099] -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

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

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

[0102] 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 slot #n1 = 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.

[0103] In the case where the PDSCH is configured to carry a maximum of 1 TB, the HARQ-ACK response may be configured in one bit. In the case where the PDSCH is configured to carry up to two TBs, the HARQ-ACK response may be configured in two bits if spatial bundling is not configured, and may 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 sent in slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0104] 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 a HARQ-ACK response sent on the PUSCH.

[0105] Spatial bundling may be supported when up to two (or two or more) TBs (or codewords) may be received at one 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 that may schedule more than four layers among the serving cells of the cell group. A UE that desires 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.

[0106] For example, assuming that a UE receives a DCI that schedules two TBs and receives the two TBs on a PDSCH based on the DCI, the UE that performs spatial bundling can generate a single A / N bit by a logical AND operation between a first A / N bit for a first TB and a second A / N bit for a 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.

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

[0108] There are multiple parallel DL HARQ processes for DL ​​transmission at the BS / UE. Multiple parallel HARQ processes enable continuous DL transmission while the BS is waiting for HARQ feedback indicating successful or failed reception of the 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 unit (PDU) transmissions, HARQ feedback for the MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0109] Figure 6 An exemplary PUSCH transmission process is shown in FIG. Figure 6 , the UE may detect the PDCCH in slot #n. The PDCCH includes DL scheduling information (eg, DCI format 1_0 or 1_1). The DCI format 1_0 or 1_1 may include the following information.

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

[0111] -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 one slot. The starting symbol and length of the PUSCH can be indicated by the start and length indicator value (SLIV) or separately.

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

[0113] Figure 7Figure 1 shows an 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.

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

[0115] When carrier aggregation is supported, one UE can send and receive signals to and from a BS in multiple aggregated cells / carriers. If multiple CCs are configured for one 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 the UCC (non-standalone (NSA) mode). In this case, the LCC may be configured as the PCC and the UCC may be configured as the SCC. If multiple LCCs are configured for the UE, one specific LCC may be configured as the PCC and the other LCCs may be configured as the SCC. Figure 8 (a) Corresponds to LAA of 3GPP LTE system. Figure 8 (b) illustrates the case where the UE and the BS send 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 can be supported in the unlicensed band of the 3GPP NR system.

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

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

[0118] – Channel Access Procedure (CAP): A process of evaluating channel availability based on sensing to determine whether the channel is used by other communication nodes before signal transmission. 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).

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

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

[0121] -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 a gap within a DL transmission burst without sensing channel availability.

[0122] -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 a gap within a UL transmission burst without sensing channel availability.

[0123] – 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 an LTE-based system, a discovery burst may be a transmission initiated by the BS, including a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS), and further including a non-zero power CSI-RS. In an NR-based system, a discovery burst may be a transmission initiated by the BS, including at least one SS / PBCH block and further including a CORESET for a PDCCH scheduling a PDSCH with SIB1, a PDSCH carrying SIB1, and / or a non-zero power CS-RS.

[0124] Fig. 9 The method of occupying resources in the unlicensed band is illustrated. According to regional regulations on unlicensed bands, communication nodes in unlicensed bands need to determine whether other communication nodes use the channel before signal transmission. Specifically, the communication node may first perform carrier sensing (CS) before signal transmission to check whether other communication nodes send signals. If it is determined that other communication nodes do not send signals, this means confirming the idle channel assessment (CCA). When there is a predefined CCA threshold or a CCA threshold configured by high-level (e.g., RRC) signaling, if energy above the CCA threshold is detected in the channel, 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. When it is determined that the channel is in an idle state, the communication node may start sending signals in the UCell. The above process may be referred to as listen before talk (LBT) or channel access process (CAP). LBT and CAP are interchangeable.

[0125] In Europe, two LBT operations are defined: frame-based equipment (FBE) and load-based equipment (LBE).

[0126] refer to Fig.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 being a time 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.

[0127] refer to Fig.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 during 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.

[0128] Table 6 illustrates an exemplary CAP supported in NR-U.

[0129] [Table 6]

[0130]

[0131]

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

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

[0134] (1) Type 1DL CAP

[0135] 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 may be applicable to the following transmissions.

[0136] - 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

[0137] - A transmission initiated by the BS with (i) only a discovery burst or with (ii) a discovery burst multiplexed with non-unicast information.

[0138] Reference Fig.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 deferral 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:

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

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

[0141] Step 3) (S1250) senses 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.

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

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

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

[0145] (2) Type 2DL CAP

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

[0147] As described previously with reference to Table 6, multiple CAP types (i.e., LBT types) may be defined for UL transmission in an 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.

[0148] (1) Type 1 UL CAP

[0149] Reference Fig.13The type 1 UL CAP of Table 6 is described in more detail. The UE may start the CAP to perform signal transmission in the unlicensed band (S1510). The UE may randomly select a backoff counter N within the contention window (CW) according to step 1. N is set to an initial value N init (S1520). 0 and CW p Any value between init . Subsequently, when the backoff counter N is 0 according to step 4 (S1530; Yes), the UE ends the CAP (S1532). Then, the UE can send a Tx burst (S1524). On the contrary, when the backoff counter is not 0 (S1530; No), the UE reduces the backoff counter by 1 according to step 2 (S1540). Subsequently, the UE checks whether the channel of the UCell is idle (S1550). When the channel is idle (S1550; Yes), the UE checks whether the backoff counter is 0 (S1530). On the contrary, when the channel is not idle, that is, when the channel is busy in step S1550 (S1550; No), the UE checks whether the channel is idle for a postponement duration T greater than the time slot duration (e.g., 9uc). d (25usec or longer) period (S1560). When the channel is idle during the deferral duration (S1570; Yes), the UE may restore the CAP. The deferral duration may include a 16-usec duration and an m p On the contrary, when the channel is busy during the deferral duration (S1570; No), the UE re-executes step S1560 to check again whether the channel is idle during the new deferral duration.

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

[0151] [Table 7]

[0152]

[0153] 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 a 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.

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

[0155] 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 ref It is subframe (or time slot) n0.

[0156] (2) Type 2 UL CAP

[0157] When the sensing duration T is at least 25us short_ul When the sensing channel is idle during this 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).

[0158] Fig.14 An exemplary case in which a plurality of LBT sub-bands (LBT-SBs) are included in an unlicensed band is illustrated. Fig.14, multiple LBT-SBs may be included in the BWP of a cell (or carrier). For example, the LBT-SB may have a band of 20 MHz. The 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-SB / RB may be configured / defined to be indexed gradually from a lower frequency band to a higher frequency band.

[0159] UE-initiated COT structure for FBE and unlicensed band operations based thereon

[0160] The present disclosure proposes a new UE-initiated COT for FBE. Those skilled in the art will appreciate that the proposed UE-initiated COT for FBE is clearly distinguishable from the BS-initiated COT or the BS / UE-initiated COT for LBE.

[0161] Before describing the new UE-initiated COT proposed for FBE, the FBE-based LBT / CAP introduced into the NR Release 16 system will be described. In NR Release 16, a fixed frame period (FFP) transmission structure (e.g., type 2A / 2B CAP) starting with BS-initiated COT has been introduced, and its key contents are summarized as follows.

[0162] 1) Information about FFP duration / period and FFP start time may be configured for the UE.

[0163] A. FFP can be configured to span one of {1, 2, 2.5, 4, 5, 10} milliseconds, including idle periods.

[0164] B. Set the start time of FFP to align with every even radio frame number.

[0165] C. The UE may determine / configure the FFP (eg, FFP position / length / start / end) based on the corresponding information (eg, FFP period / FFP start time).

[0166] 2) In NR Release 16, FFP-related COT generation / initiation can only be performed by the BS, and a structure is adopted in which each FFP starts with a BS-initiated COT.

[0167] A. The UE may send configured UL resources (e.g., PRACH or PUSCH) in the same FFP, FFP#i only when the UE successfully detects a specific DL signal (e.g., SSB, SIB, UE (group) common PDCCH (GC-PDCCH) and / or UE-specific PDCCH) from the BS in FFP#i.

[0168] B. Transmission by a BS that has directly generated a COT / FFP may be defined as (BS)-initiated COT transmission, and transmission by a UE based on detection of a DL signal from the BS within the COT / FFP generated by the BS may be defined as shared COT-based transmission.

[0169] 3) The BS may generate a BS-initiated COT by performing LBT during a predetermined time (eg, 25 usec) shortly before the FFP.

[0170] A. The UE and the BS may perform UL / DL transmission in the FFP period by performing 16-usec LBT or 25-usec LBT according to the size of a DL-to-UL gap or a UL-to-UL gap in the FFP period.

[0171] In Release 17, it is possible to consider introducing an FFP transmission structure starting with UE-initiated COT to effectively support URLLC services in a U-band environment based on FBE. To this end, the following operation method is proposed.

[0172] A proposal for UE-initiated COT for FBE will be described below. In the following description, a DL signal may mean a specific DL signal according to the context.

[0173] [Proposal 1]

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

[0175] 2) The UE may be defined / configured to perform LBT shortly before the start time of its FFP-u (eg, during 25usec, 9usec, or 16usec).

[0176] A. When the channel is determined to be idle as a result of LBT, the UE may start corresponding FFP-u transmission in a UE-initiated COT.

[0177] i. For example, the BS may be defined / configured to be able to perform DL transmission in the FFP-u period under specific conditions (e.g., by sharing a UE-initiated COT). As an example of a specific condition for DL ​​transmission of the BS, a BS operation may be defined in which the BS is able to perform DL transmission (in the form of a shared COT-based transmission) in the same FFP-u period only when the BS successfully detects a specific UL channel (e.g., PUSCH / PUCCH DMRS, PRACH, or SRS) from the UE.

[0178] B. When the channel is determined to be busy as a result of LBT, assuming that the FFP-g transmission structure starts with a BS-initiated COT (for the FFP-g period including the FFP-u start time), the UE may perform the aforementioned Release 16 operation as an exemplary UE operation.

[0179] i. In a specific example, the UE may be defined / configured to be able to perform a configured UL (e.g., PRACH or PUSCH) transmission in an FFP-g period only when the UE successfully detects a specific DL signal from the BS in the same FFP-g period. For example, when the UE fails to detect a DL signal in an FFP-g period, the UE may be defined / configured not to be allowed to perform UL transmission.

[0180] 3) Alternatively, the UE operation may be defined / configured to detect a DL signal for an FFP-g period preceding the start time of its FFP-u (in an FFP-g period including the start time of its FFP-u).

[0181] A. When a DL signal cannot be detected within the FFP-g period before its FFP-u start time, the UE may perform LBT shortly before its FFP-u start time (eg, during 25usec, 9usec, or 16usec).

[0182] i. When the channel is determined to be idle as a result of LBT, the UE may start FFP-u transmission in a UE-initiated COT.

[0183] ii. Conversely, when the channel is determined to be busy as a result of LBT, assuming that the FFP-g transmission structure starts from a BS-initiated COT, UE operation can be defined in which the UE does not perform transmission (and / or does not receive) during the FFP period, or the UE can perform the aforementioned Release 16 operation.

[0184] B. When a DL signal is successfully detected in an FFP-g period prior to the start time of its FFP-u, the UE may perform Release 16 operation assuming an FFP-g transmission structure starting from a BS-initiated COT.

[0185] C. For example, before starting FFP-u transmission / UE-initiated COT configuration, the UE may attempt to detect DL signals based on the previous FFP-g (including the start time of FFP-u) in the time domain, and give priority to transmission based on shared COT based on DL signal detection. For example, when the UE is able to share the previous BS-initiated COT and send its UL signal in the BS-initiated COT, the UE may skip the UE-initiated COT configuration (and LBT therefor).

[0186] 4) In case the UE is configured with multiple LBT-SBs (eg, RB sets (+ protection RBs)) and / or multiple carriers, the following operations may be considered.

[0187] A. When (for a specific FFP period / start time), the UE determines that the channel is busy in at least one LBT-SB or at least one carrier (and the UE detects a DL signal from the BS) (i) as a result of LBT for an LBT-SB group including multiple LBT-SBs in one carrier (and / or multiple intra-band carriers), (ii) as a result of LBT for a carrier group including multiple intra-band carriers, or (iii) as a result of LBT for an LBT-SB group / carrier group indicated as available through the same bit of the corresponding PDCCH, when the availability for the LBT-SB / carrier is indicated by specific signaling (e.g., GC-PDCCH), the UE may (for that FFP period / start time) perform the above-mentioned Release 16 operation for all LBT-SBs / carriers in the LBT-SB group / carrier group to which the corresponding LBT-SB / carrier belongs, assuming an FFP-g transmission structure starting with BS-initiated COT. Alternatively, when at least one LBT-SB / carrier is indicated to be available (based on BS-initiated COT generation / configuration) by specific signaling (e.g., GC-PDCCH) (regardless of the LBT result), the UE may (for that FFP period / start time) perform the aforementioned Release 16 operations for all LBT-SBs / carriers in the LBT-SB group / carrier group to which the corresponding LBT-SB / carrier belongs, assuming an FFP-g transmission structure starting with BS-initiated COT.

[0188] i. Therefore, the UL resources (e.g., (CG)PUSCH, PRACH, or PUCCH) configured at the FFP-u start time (based on the detected DL signal or the indication of the GC-PDCCH included in the FFP-g period (starting with the BS-initiated COT)) in the LBT-SB / carrier of the LBT-SB group / carrier group (including the LBT-SB / carrier in which the channel is busy as a result of LBT, the LBT-SB / carrier in which the BS's DL signal is detected, or the LBT-SB / carrier indicated as available through the GC-PDCCH) may be canceled or processed as invalid; and / or the UE may be enabled / allowed to perform a shared COT-based transmission based on the BS-initiated COT in the UL resources (e.g., PUSCH or PUCCH) configured or scheduled at the FFP-u start time; and / or the UE may be enabled / allowed to perform only a one-time transmission without UE-initiated COT generation / configuration (e.g., the BS is not enabled to perform DL transmission in the form of a shared COT-based transmission based on the corresponding transmission).

[0189] ii. Therefore, for an FFP assumed to be FFP-g (the entire LBT-SB group / carrier group in the corresponding period), the UE may not be allowed to configure / send FFP-u through UE-initiated COT generation (or the UE may be allowed to perform only shared COT transmissions in the corresponding FFP period). This may be intended to prevent UE transmissions based on UE-initiated COT from causing (UL to DL) interference to BS-initiated COT / FFP. For example, collision / interference between BS-initiated COT and UE-initiated COT may be prevented.

[0190] iii. Fig.15 An exemplary UE operation is shown. Fig.15, the UE operation method may vary depending on whether the availability of the corresponding SB / carrier group has been indicated (e.g., via GC-PDCCH) (E05). For example, the UE may receive availability indication information from the BS via specific signaling. The specific signaling may be, but is not limited to, PDCCH or GC-PDCCH. In a more specific example, the availability indication information may be included in DCI format 2_0 delivered on GC-PDCCH. The availability indication information may include one or two bits, and each bit may be associated with an SB group / carrier group. For example, the nth bit may indicate the availability for SB / carrier group #n. When the UE receives an availability indication indicating that the corresponding SB / carrier group is available, the UE may operate based on version 16 FFP-g for at least all SBs / carriers in the SB / carrier group (regardless of LBT) (E25). Conversely, in the absence of the above-mentioned availability indication (on GC-PDCCH), the UE may operate based on the result of the LBT (performed in operation E10). For example, when it is determined that the channel is busy in a specific SB / carrier as a result of LBT (and a DL signal is detected from the BS in the specific SB / carrier), the UE can perform Release 16 FFP-g operations for all SBs / carriers of the SB / carrier group to which the corresponding SB / carrier belongs (E25).

[0191] B. Otherwise, only when it is determined that the channel is idle in all LBT-SBs or all carriers as a result of LBT for a group of LBT-SBs or a group of carriers (e.g., Fig.15 In the case where no DL signal from the BS is detected in any LBT-SB / carrier, and none of the LBT-SB / carriers is indicated as available by the GC-PDCCH, the UE may start FFP-u transmission in the UE-initiated COT in the LBT-SB / carrier group (all or part of the LBT-SB / carriers, e.g., some LBT-SB / carriers that the LBT result indicates are idle) (e.g., Fig.15 in E20).

[0192] C. In addition, in the case of scheduled UL (e.g., PUSCH or PUCCH) transmission, the DCI indicates whether the UL transmission is a UE-initiated COT-based transmission or a shared COT-based transmission (BS-initiated COT-based) (transmission type), and for configured UL (e.g., PUSCH or PUCCH) transmission, whether the UL transmission is a UE-initiated COT-based transmission or a shared COT-based transmission (BS-initiated COT-based) (transmission type) is determined according to a specific rule (hereinafter referred to as "RULE_#1"), and the following UE operations can be considered.

[0193] i. When the DCI indicates shared COT-based transmission for a specific scheduled UL resource, the UE is able to send the specific scheduled UL resource in the form of shared COT-based transmission assuming that the BS has started BS-initiated COT transmission (while discarding DL signal detection) in the FFP-g period including the UL resource, or the UE is able to send the UL resource in the form of shared COT-based transmission only when the UE detects a DL signal (based on BS-initiated COT transmission) in the FFP-g including the UL resource (when the UE fails to detect the DL signal, the UE is not able to send the UL resource).

[0194] ii. In the example of RULE_#1, when the indication that the configured UL resources are time-aligned with the start of a specific FFP-u period, the specific FFP-g period includes the start time of the FFP-u period (or the configured UL resources), and the UE detects a DL signal (sent based on the BS-initiated COT) in the FFP-g, the UE may send the configured UL resources based on the shared COT, and otherwise, based on the UE-initiated COT (for convenience, this rule is defined as "C-UL rule-a". C-UL rule-a may also be applied to RULE_#2, RULE_#3 and / or any RULE_#i to be described later, not limited to RULE_#1).

[0195] iii. In the example of RULE_#1, when the configured UL resources are indicated to be aligned with the start time of a specific FFP-u period, the UE can always send the configured UL resources based on the UE-initiated COT (for convenience, this rule is defined as "C-ULrule-b". C-UL rule-b can also be applied to RULE_#2, RULE_#3 and / or any RULE_#i to be described later, not limited to rule 1).

[0196] iv. In the example of RULE_#1, when the configured UL resources are indicated to be included in a specific FFP-u period without being aligned with the start time of the FFP-u period, and the UE has started to send transmission based on the UE-initiated COT within the FFP-u period, the UE may send the configured UL resources based on the UE-initiated COT. Otherwise, when a specific FFP-g period includes the configured UL resources and the UE detects a DL signal (sent based on the BS-initiated COT) in the FFP-g, the UE may send the configured UL resources based on the shared COT (for convenience, this rule is defined as "C-UL rule-c". C-UL rule-c may also be applied to RULE_#2, RULE_#3 and / or any RULE_#i to be described later, not limited to RULE_#1).

[0197] v. In the above state, in the case where RULE_#1 is applied to a specific configured UL resource in a specific carrier (carrier #1) at a specific time, when it is assumed that the configured UL transmission is a specific transmission type (e.g., UE-initiated COT-based transmission), and DCI indicates another transmission type (e.g., shared COT-based transmission (without LBT)) of a specific scheduled UL transmission in another carrier (carrier #2) (adjacent to carrier #1 in frequency), the UE may apply the transmission type indicated by the DCI (e.g., shared COT-based transmission) to the configured UL transmission (as well as the scheduled UL transmission). In another method, the UE may perform only the scheduled UL transmission and discard the configured UL transmission.

[0198] 1. In another method, when it is determined that the transmission type assumed for the configured UL transmission is different from the transmission type indicated by the DCI for the scheduled UL transmission in the above state, the UE can perform shared COT-based transmission for both UL transmissions (or UE-initiated COT-based transmission for both UL transmissions).

[0199] D. In addition, in the case of determining whether to perform configured UL (e.g., PUSCH or PUCCH) transmission based on UE-initiated COT or shared COT (transmission type) according to a specific rule (hereinafter, referred to as "RULE_#2"), the following UE operations may be considered.

[0200] i. In the example of RULE_#2, the C-UL rule-a defined above can be used. When the configured UL resources are aligned with the start time of a specific FFP-u period, the specific FFP-g period includes the start time of the FFP-u period (or the configured UL resources), and the UE detects a DL signal in FFP-g (sent based on the COT initiated by the BS), the UE can send the configured UL resources based on the shared COT, and otherwise, send based on the COT initiated by the UE.

[0201] ii. In the example of RULE_#2, the aforementioned defined C-UL rule-b may be used. When the configured UL resources are indicated to be aligned with the start time of a specific FFP-u period, the UE may always send the configured UL resources based on the UE-initiated COT.

[0202] iii. In the example of RULE_#2, the aforementioned defined C-UL rule-c may be used. When the configured UL resources are indicated as being included in a specific FFP-u period without being aligned with the start time of the FFP-u period, and the UE has started sending transmissions based on UE-initiated COT in the FFP-u period, the UE may send the configured UL resources based on the UE-initiated COT. Otherwise, when a specific FFP-g period includes the configured UL resources and the UE detects a DL signal (sent based on the BS-initiated COT) in FFP-g, the UE may send the UL resources based on the shared configured UL resources.

[0203] v. In the above state, in the case where RULE_#2 is applied to a specific configured UL resource (configured UL#1) in a specific carrier (carrier #1) at a specific time, it is determined that a specific transmission type (e.g., UE-initiated COT-based transmission) is assumed for configured UL#1, and when RULE_#2 is simultaneously applied to a specific configured UL resource (configured UL#2) in another carrier (carrier #2) (adjacent to carrier #1 in frequency), it is determined that another transmission type (e.g., shared-COT-based transmission) is assumed for configured UL#2, the UE may perform shared-COT-based transmission for both UL transmissions (or UE-initiated COT-based transmission for both UL transmissions). In another method, in the above situation, the UE may perform only the configured UL transmission determined as the shared-COT-based transmission, and discard the configured UL transmission determined as the UE-initiated COT-based transmission.

[0204] E. In addition, in the case where the configured UL (eg, PUSCH or PUCCH) resources are configured to be aligned with the start time of a specific FFP-u period, the following operations may be performed.

[0205] i. When a specific FFP-g period includes the start time of the FFP-u period (or the configured UL resources), and in the FFP-g period or in the period between the start time of the FFP-g period and the configured UL resources, specific DL resources (e.g., semi-statically configured DL symbols) and / or specific DL transmissions (e.g., periodically configured SSBs (for SS / PBCH broadcasts) and / or specific CORESETs (e.g., with the lowest ID / index) and / or TRS / CSI-RS transmissions and / or PDSCH transmissions) are pre-configured / pre-indicated before the start of the FFP-g period, the UE may apply the aforementioned rule C-UL rule-a to the configured UL resources.

[0206] ii. Otherwise, (for example, although the FFP-g period includes the start time of the FFP-u period (or the configured UL resources), specific DL resources and / or DL ​​transmissions in the FFP-g period or in the period between the start time of the FFP-g period and the configured UL resources are not pre-configured / pre-indicated before the start of the FFP-g period), the UE may apply the aforementioned rule C-UL rule-b to the configured UL resources.

[0207] F. In addition, in the case where the configured UL (eg, PUSCH or PUCCH) resources are configured to be aligned with the start time of a specific FFP-u period, the following operations may be performed.

[0208] i. When a specific FFP-g period includes the start time of the FFP-u period (or the configured UL resource), and the interval between the start time of the FFP-g period and the configured UL resource (the start offset of the FFP-u period set based on the even radio frame index) is equal to or greater than a specific value, the UE may apply the aforementioned rule C-UL rule-a to the configured UL resource. Otherwise (for example, when the interval (or FFP-u offset) is less than a specific value), the UE may apply the aforementioned rule C-UL rule-b to the configured UL resource.

[0209] ii. Alternatively, on the contrary, when the specific FFP-g period includes the start time of the FFP-u period (or the configured UL resource), and the interval between the start time of the FFP-g period and the configured UL resource (or the start offset of the FFP-u set based on the even radio frame index) is less than a specific value, the UE may apply the aforementioned rule C-UL rule-a to the configured UL resource. Otherwise (for example, when the interval (or FFP-u offset) is equal to or greater than a specific value), the UE may apply the aforementioned rule C-UL rule-b to the configured UL resource.

[0210] G. In addition, in the case where the DCI indicates whether scheduled UL (eg, PUSCH or PUCCH) transmission (transmission type) is performed based on UE-initiated COT or shared COT, the following UE operations may be considered.

[0211] i. For a specific scheduled UL resource (scheduled UL#1) in a specific carrier (carrier #1) at a specific time point, when DCI indicates a specific transmission type (e.g., UE-initiated COT-based transmission), and for a specific scheduled UL resource (scheduled UL#2) in another carrier (carrier #2) (adjacent to carrier #1 in frequency) at the same time point, DCI indicates another transmission type (e.g., shared COT-based transmission (without LBT)), the UE may perform shared COT-based transmission for these two UL resources (or UE-initiated COT-based transmission for these two UL resources). In another method, the UE may perform only the scheduled UL transmission indicated as the shared COT-based transmission, and discard the scheduled UL transmission indicated as the UE-initiated COT-based transmission in the above case.

[0212] 1. In another method, when the DCI indicates different transmission types for scheduled UL#1 and scheduled UL#2 in the same state as above, the UE can apply the transmission type indicated by the later received DCI (among the two DCIs) for the two UL resources (or the transmission type indicated by the earlier received DCI).

[0213] In another method, in the above situation, the UE may perform only the scheduled UL transmission indicated by the DCI received later, and discard the scheduled UL transmission indicated by the DCI received earlier.

[0214] H. In addition, when the non-fallback DCI (DCI format 0_1 ​​or 0_2) indicates whether the UL (i.e., non-fallback UL) transmission scheduled by the non-fallback DCI is a UE-initiated COT-based transmission or a shared COT-based transmission (transmission type), and whether the UL transmission scheduled by the fallback DCI (e.g., DCI format 0_0) is a UE-initiated COT-based transmission or a shared COT-based transmission (transmission type) is determined according to a specific rule (hereinafter referred to as "RULE_#3"), the following UE operations can be considered.

[0215] i. In the example of RULE_#3, when the scheduled UL resources are indicated to be aligned with the start time of a specific FFP-u period, the specific FFP-g period includes the start time of the FFP-u period (or the scheduled UL resources), and the UE detects a DL signal (sent based on the BS-initiated COT) in the FFP-g, the UE may send the scheduled UL resources based on the shared COT, and otherwise, send based on the UE-initiated COT (for convenience, this rule is defined as "S-UL rule-a").

[0216] iii. In the example of RULE_#3, when the scheduled UL resources are indicated to be aligned with the start time of a specific FFP-u period, the UE may always send the scheduled UL resources based on the UE-initiated COT (this rule is defined as “S-UL rule-b”).

[0217] iv. In the example of RULE_#3, when the scheduled UL resources are indicated as being included in a specific FFP-u period without being aligned with the start time of the FFP-u period, and the UE has started transmission based on the UE-initiated COT in the FFP-u period, the UE may send the scheduled UL resources based on the UE-initiated COT. Otherwise, when a specific FFP-g period includes scheduled UL resources and the UE detects a DL signal (sent based on the BS-initiated COT) in FFP-g, the UE may send the scheduled UL resources based on the shared COT (this rule is defined as "S-UL rule-c").

[0218] iv. In the above state, in the case where RULE_#3 is applied to a specific fallback UL transmission in a specific carrier (carrier #1) at a specific time point, when it is determined that a specific transmission type (e.g., transmission based on a COT initiated by the UE) is assumed for the fallback UL transmission, and for a specific non-fallback UL transmission in another carrier (carrier #2) (adjacent to carrier #1 in frequency), the DCI indicates another transmission type (e.g., transmission based on a shared COT (without LBT)), the UE may apply the transmission type indicated by the DCI (e.g., transmission based on a shared COT) to the fallback UL transmission (as well as the non-fallback UL transmission). In another method, the UE may perform only the non-fallback UL transmission and discard the fallback UL transmission.

[0219] 1. In another method, in the same state as above, when it is determined that the transmission type assumed for the fallback UL transmission is different from the transmission type indicated by the DCI for the non-fallback UL transmission, the UE may perform a shared COT-based transmission for the two UL transmissions (or a UE-initiated COT-based transmission for the two UL transmissions).

[0220] I. In addition, in a case where the DCI indicates whether scheduled UL (eg, PUSCH or PUCCH) transmission (transmission type) is performed based on UE-initiated COT or shared COT, the following operations may be performed.

[0221] i. When the scheduled UL resources are indicated to be aligned with the start time of a specific FFP-u period, the UE may send the scheduled UL resources by applying the transmission type indicated by the DCI (eg, UE-initiated COT-based transmission or shared COT-based transmission).

[0222] ii. Otherwise (when the scheduled UL resources are indicated as not aligned with the start time of a specific FFP-u period or are not indicated as aligned with the start time of a specific FFP-u period), the UE may apply the aforementioned rule S-UL rule-c to the scheduled UL resources (while ignoring the transmission type indicated by the DCI).

[0223] J. In addition, in a case where the DCI indicates whether scheduled UL (eg, PUSCH or PUCCH) transmission (transmission type) is to be performed based on UE-initiated COT or shared COT, the following operations may be performed.

[0224] i. When the scheduled UL resources are indicated to be aligned with the start time of a specific FFP-u period, the UE may send the scheduled UL resources by applying the transmission type indicated by the DCI (eg, UE-initiated COT-based transmission or shared COT-based transmission).

[0225] ii. Otherwise (when the scheduled UL resources are indicated as not aligned with the start time of a specific FFP-u period or are not indicated as aligned with the start time of a specific FFP-u period), if the DCI indicates transmission based on a shared COT as the transmission type, the UE may send the scheduled UL resources based on the shared COT. If the DCI indicates transmission based on a UE-initiated COT as the transmission type, the UE may apply the aforementioned rule S-UL rule-c to the scheduled UL resources.

[0226] K. In addition, in the case where DCI does not explicitly indicate whether scheduled UL (eg, PUSCH or PUCCH) transmission (transmission type) is performed based on UE-initiated COT or shared COT, the following operations may be performed.

[0227] i. When the DCI indicates to discard LBT operation (ie, no LBT), the UE may send scheduled UL resources based on the shared COT.

[0228] ii. Otherwise (when the DCI indicates LBT operation), if the scheduled UL resources are indicated as aligned with the start time of a specific FFP-u period, the UE may apply the aforementioned rule S-UL rule-a or S-UL rule-b (applied to the scheduled UL resources). Otherwise, when the scheduled UL resources are indicated as not aligned with the start time of a specific FFP-u period or are not indicated as aligned with the start time of a specific FFP-u period, the UE may apply the aforementioned rule S-UL rule-c (applied to the scheduled UL resources).

[0229] L. By applying the aforementioned rule C-UL rule-b or C-UL rule-a (and / or S-UL rule-b or S-UL rule-a) to the UL resources, in a case where the configured (and / or scheduled) UL resource UL#1 configured / indicated to be aligned with the start time of the FFP-u period is determined / operated to be transmitted based on the UE-initiated COT, when the specific scheduled (and / or configured) UL resource UL#2 is indicated / configured to overlap with the idle period of FFP-u shortly before UL#1, the UE can assume / perform shared COT-based transmission for UL#1, in an exceptional case where UE-initiated COT-based transmission is not assumed / performed (or the UE may not be allowed to transmit UL#1).

[0230] i. The above operation can be equally applied to the case where rule C-UL rule-a (and / or S-UL rule-a) is applied to UL#1.

[0231] ii. This operation may always be applied regardless of whether the UE has sent UL#2, discarded the transmission of UL#2, or failed in the transmission of UL#2. Alternatively, this operation may be applied only when the UE has actually sent UL#2, but when the UE has discarded or failed in the transmission of UL#2, the UE may assume / perform a transmission based on UE-initiated COT by applying rule C-UL rule-b (and / or S-UL rule-b) to UL#1 (or the UE may send UL#1 by applying rule C-UL rule-a (and / or S-UL rule-a)).

[0232] iii. Alternatively, in the case where the UE is configured to apply rule C-UL rule-b or C-UL rule-a (and / or S-UL rule-b or S-UL rule-a) to the configured (and / or scheduled) UL resource UL#1, when a specific scheduled (and / or configured) UL resource UL#2 is indicated / configured to be shortly before UL#1 and separated from UL#1 by a gap equal to or less than X microseconds (e.g.: X=9, 16 or 25), the UE may assume / perform a shared COT-based transmission for UL#1, with the exception that a UE-initiated COT-based transmission is not assumed / performed (or the UE may not be allowed to send UL#1).

[0233] 1. The above UE operation can be equally applied to the case where rule C-UL rule-a (and / or S-UL rule-a) is applied to UL#1.

[0234] 2. This operation may always be applied regardless of whether the UE has sent UL#2, discarded the transmission of UL#2, or failed in the transmission of UL#2. Alternatively, this operation may be applied only when the UE has actually sent UL#2, however when the UE has discarded or failed in the transmission of UL#2, the UE may assume / perform a transmission based on UE-initiated COT by applying rule C-UL rule-b (and / or S-UL rule-b) to UL#1 (or the UE may send UL#1 by applying rule C-UL rule-a (and / or S-UL rule-a)).

[0235] M. In the case where the DCI indicates shared COT-based transmission for the scheduled UL resources scheduled to be aligned with the start time of the FFP-u period, when a specific FFP-g period includes the start time of the FFP-u period (or scheduled UL resources) and the UE detects a DL signal (sent based on the BS-initiated COT) in the FFP-g, the UE may perform shared COT-based transmission in the scheduled UL resources, and otherwise, the UE may not be allowed to transmit the scheduled UL resources.

[0236] i. In addition, in the case where the DCI indicates UE-initiated COT-based transmission for scheduled UL resources that are scheduled to be included in the FFP-u period but not aligned with the start time of the FFP-u period, when the UE has already started the UE-initiated COT-based transmission in the FFP-u period, the UE may perform the UE-initiated COT-based transmission in the scheduled UL resources, otherwise (i.e., when the UE has not yet started the UE-initiated COT-based transmission in the FFP-u period), the UE may discard the transmission of the scheduled UL resources (i.e., the corresponding transmission may not be allowed).

[0237] N. In another method, in a case where the DCI indicates a shared COT-based transmission for a scheduled UL resource that is scheduled to be aligned with the start time of the FFP-u period, when the UE detects a DL signal (sent based on a BS-initiated COT) by applying S-UL rule-a (and / or C-UL rule-a) to the UL resources, the UE may perform the shared COT-based transmission in the scheduled UL resources, and otherwise, the UE may perform the UE-initiated COT-based transmission in the scheduled UL resources.

[0238] i. The above UE operation can be applied only when the scheduled UL resources and the DCI scheduling the scheduled UL resources are sent in different FFP-g periods. Otherwise (for example, when the scheduled UL resources and the DCI scheduling the scheduled UL resources are sent in the same FFP-g period), the UE may be allowed / enabled to perform only shared COT-based transmission (based on DL signal detection) in the UL resources (indicated by the DCI to be sent based on the shared COT). When the DCI indicates a UE-initiated COT-based transmission for the scheduled UL resources, the UE may perform a UE-initiated COT-based transmission (as indicated by the DCI), and this operation may always be applied regardless of whether the scheduled UL resources and the DCI scheduling the scheduled UL resources are sent in the same or different FFP-g periods.

[0239] ii. In addition, in the case where the DCI indicates UE-initiated COT transmission based on a schedule for UL resources configured to be included in the FFP-u period but not aligned with the start time of the FFP-u period, when the UE has started UE-initiated COT transmission based on the UE by applying the S-UL rule-c (and / or C-UL rule-c) to the corresponding UL resources, the UE can perform UE-initiated COT transmission based on the UE, otherwise, when the UE has detected a DL signal (sent based on the BS-initiated COT), the UE can perform shared COT based transmission.

[0240] 1. The above UE operation may be applied only when the scheduled UL resources and the DCI scheduling the scheduled UL resources are sent in different FFP-g periods. Otherwise (e.g., when the scheduled UL resources and the DCI scheduling the scheduled UL resources are sent in the same FFP-g period), the UE may be allowed / enabled to perform only UE-initiated COT-based transmissions in the corresponding UL resources (indicated by the DCI to be sent based on the UE-initiated COT). When the DCI indicates a shared COT-based transmission for the scheduled UL resources, the UE may perform a shared COT-based transmission (as indicated by the DCI), and this operation may always be applied regardless of whether the scheduled UL resources and the DCI scheduling the scheduled UL resources are sent in the same or different FFP-g periods.

[0241] iii. In another method, in a case where the DCI indicates UE-initiated COT-based transmission or shared COT-based transmission for a scheduled UL resource configured to be included in the FFP-u period without being aligned with the start time of the FFP-u period, the UE may perform UE-initiated COT-based transmission when the UE has applied S-UL rule-c (and / or C-UL rule-c) to the corresponding UL resource without applying (and ignoring) the DCI indication, and otherwise, when the UE has detected a DL signal (sent based on the BS-initiated COT), the UE may perform shared COT-based transmission.

[0242] 1. The above UE operation may be applied only when the scheduled UL resources and the DCI scheduling the scheduled UL resources are sent in different FFP-g periods. Otherwise (e.g., when the scheduled UL resources and the DCI scheduling the scheduled UL resources are sent in the same FFP-g period), the UE may send the scheduled UL resources based on the transmission type indicated by the DCI (e.g., UE-initiated COT transmission or shared COT-based transmission) (e.g., UE-initiated COT transmission or shared COT-based transmission).

[0243] O. For configured (and / or scheduled) UL resources that are configured / indicated to be aligned with the start time of the FFP-g period (and / or after a predetermined time or less from the start time), transmission based only on UE-initiated COT may be allowed / enabled.

[0244] i. This may be because in order to perform UL transmission based on shared COT, the (minimum) processing time of the UE required to detect the DL signal (sent based on the BS-initiated COT) should be ensured before the UL transmission.

[0245] ii. Therefore, for the configured (and / or scheduled) UL resources that are configured / indicated not to be aligned with the start time of the FFP-g period (and / or after a time greater than a specific time from the start time), the UE may send the UL resources based on a shared COT or a UE-initiated COT by applying rules C-UL rule-a (and / or S-UL rule-a), C-UL rule-b (and / or S-UL rule-b), or C-UL rule-c (and / or S-UL rule-c) or based on an indication of the DCI, depending on the situation.

[0246] P. When the UE performs transmission in the configured (and / or scheduled) UL resources that are configured / indicated to be aligned with the start time of the FFP-u period (and / or after a specific time or less from the start time) by applying rule C-UL rule-a (and / or S-UL rule-a), CP extension applied / performed for transmitting the UL resources and / or parameter values ​​for CP extension (e.g., the following CP extension operation (i.e., CPE behavior 1 / 2)) may be determined / configured / applied differently, depending on whether the UL resources are sent based on a shared COT (based on BS-initiated COT) or a UE-initiated COT.

[0247] i. CPE behavior 1: The UE may perform CP extension by using / applying a CP extension parameter value (e.g., extended CP length) configured by the BS or by using / applying a specific candidate CP extension parameter value from among a plurality of preconfigured candidate CP extension parameter values ​​(e.g., a candidate CPE value set) indicated by the DCI.

[0248] ii. CPE behavior 2: CP extension can be performed (by determining / applying the extended CP length) so that the signal start time of the UL resource accurately matches the start time of FFP-u.

[0249] iii. When the UE determines a transmission based on a shared COT for the configured (and / or scheduled) UL resources by applying rule C-UL rule-a (and / or S-UL rule-a), the UE may apply CPE behavior 1, however, when the UE determines a transmission based on a UE-initiated COT, the UE may apply CPE behavior 2.

[0250] 1. When the UE determines transmission based on UE-initiated COT by applying rule C-UL rule-b (and / or S-UL rule-b) for the configured (and / or scheduled) UL resources, the UE may apply CPE behavior 2.

[0251] iv. In addition, when the DCI indicates a shared COT-based transmission for scheduled UL resources that are scheduled to be aligned with the start time of the FFP-u period (and / or after a specific time or less from the start time), the UE may apply CPE behavior 1, however when the DCI indicates a UE-initiated COT-based transmission, the UE may apply CPE behavior 2 (while ignoring the CPE parameter value indicated by the DCI).

[0252] v. In addition, when the UE determines, by applying rule C-UL rule-c (and / or S-UL rule-c), a shared COT-based transmission for configured (and / or scheduled) UL resources that are configured / indicated to be included in the FFP-u period but not aligned with the start time of the FFP-u period, the UE may apply CPE behavior 1, however, when the UE determines a UE-initiated COT-based transmission, the UE may apply CPE behavior 2.

[0253] 1. Alternatively, in this case, the UE may apply CPE Behavior 1 to both the case where a shared COT-based transmission is determined for UL resources and the case where a UE-initiated COT-based transmission is determined for UL resources.

[0254] vi. In addition, when the DCI indicates a shared COT-based transmission for scheduled UL resources that are scheduled to be included in the FFP-u period but not aligned with the start time of the FFP-u period, the UE may apply CPE behavior 1, however, when the DCI indicates a UE-initiated COT-based transmission for scheduled UL resources, the UE may apply CPE behavior 2 (while ignoring the CPE parameter value indicated by the DCI).

[0255] 1. Alternatively, in this case, the UE may apply CPE Behavior 1 to both the case where a shared COT-based transmission is determined for UL resources and the case where a UE-initiated COT-based transmission is determined for UL resources.

[0256] Q. (For a specific FFP period / start time) the LBT-SB group / carrier group on which the UE performs LBT may be determined as all of the multiple LBT-SBs configured / constructed in one carrier (and / or multiple in-band carriers) or multiple in-band carriers, or may be determined / limited to the LBT-SB / carrier in which (for the corresponding FFP period / start time) the UE is to perform actual UL channel / signal transmission or the LBT-SB / carrier configured / indicated for UL channel / signal transmission from the UE. For example, when there are LBT-SB groups / carrier groups #0 to #N in the system, and the UE intends to perform UL channel / signal transmission in some of the LBT-SB groups / carrier groups #0 to #N (hereinafter referred to as specific LBT-SB groups / carrier groups) or is configured / indicated to perform UL channel / signal transmission, the UE may be allowed to start FFP-u transmission in the UE-initiated COT based on the entire specific LBT-SB group / carrier group being idle.

[0257] R. In further generalization, in order to start corresponding FFP-u transmission in the COT initiated by the UE in the presence of LBT-SB groups / carrier groups #0 to #N in the system, at least some LBT-SB groups / carrier groups in which LBT idle should be confirmed can be configured / indicated / determined for the UE. For example, based on the LBT result of a specific LBT-SB group / carrier group being confirmed as idle, the UE can be allowed to start FFP-u transmission in the COT initiated by the UE, restricted to a specific LBT-SB group / carrier group or for an LBT-SB group / carrier group including a specific LBT-SB / carrier group. When the UE starts FFP-u transmission in this manner, the LBT-SB / carrier group can be defined as necessarily including the corresponding UL signal. For example, the LBT-SB / carrier group can be configured as cell common / UE group common or predefined.

[0258] 5) In addition, in the case where the UE is configured with multiple LBT-SBs (e.g., RB sets (+ protection RBs)) and / or multiple carriers (e.g., in the case where the UE operates only in BS-initiated COT-based FFP-g in the same / similar manner as the legacy Release 16 or in the state where the UE is not configured with UE-initiated COT-based FFP-u related parameters (e.g., time period and starting offset), for UL transmission in the form of shared COT-based UL transmission based on BS-initiated COT, the following operations may be considered.

[0259] A. In a case where an LBT-SB group including multiple LBT-SBs in one carrier (and / or multiple in-band carriers), a carrier group including multiple in-band carriers, or an LBT-SB group / carrier group indicated as available by the same bit of the corresponding PDCCH when availability is indicated for the LBT-SB / carrier by specific signaling (e.g., GC-PDCCH) is given / configured, when a specific LBT-SB#1 / carrier#1 is indicated as available by GC-PDCCH (e.g., sent in the authorized band), and when a DL signal is detected from the BS in at least one other LBT-SB#2 / carrier#2 within the LBT-SB group / carrier group to which LBT-SB#1 / carrier#1 belongs, the UE can be enabled / allowed to perform shared COT (UL)-based transmission (based on BS-initiated COT) for UL resources (e.g., (CG)PUSCH, PRACH, or PUCCH) configured in LBT-SB#1 / carrier#1.

[0260] i. In this case, the UE can perform UL transmission in LBT-SB #1 / carrier #1 based on the detection time of the DL signal in LBT-SB #2 / carrier #2 (by determining the DL to UL gap and performing 16-usec or 25-usec LBT according to the size of the gap).

[0261] B. Otherwise, in the case where a specific LBT-SB / carrier, LBT-SB#1 / carrier #1 is indicated by the GC-PDCCH as available (e.g., sent in the granted band), when no DL signal from the BS is detected in any other LBT-SB / carrier within the LBT-SB group / carrier group to which LBT-SB#1 / carrier #1 belongs, the UE may not be allowed to perform shared COT-based (UL) transmission (based on BS-initiated COT) for the UL resources (e.g., (CG)PUSCH, PRACH, or PUCCH) configured in LBT-SB#1 / carrier #1.

[0262] C. In the above example, the LBT-SB group / carrier group in which the UE performs LBT (for a specific FFP period / start time) may be determined to be all of the multiple LBT-SBs configured / constructed in one carrier (and / or multiple in-band carriers) or multiple in-band carriers, or may be determined / limited to the LBT-SB / carrier in which the UE (for a specific FFP period / start time) is to perform actual UL channel / signal transmission or the LBT-SB / carrier configured / indicated for UL channel / signal transmission from the UE. For example, when there are LBT-SB groups / carrier groups #0 to #N in the system, and the UE intends to perform UL channel / signal transmission or is configured / indicated to perform UL channel / signal transmission in some LBT-SB groups / carrier groups #0 to #N (hereinafter referred to as specific LBT-SB groups / carrier groups), the UE may be allowed to start FFP-u transmission in a UE-initiated COT based on the entire specific LBT-SB group / carrier group being idle.

[0263] D. In further generalization, in order to start corresponding FFP-u transmission in the COT initiated by the UE in the presence of LBT-SB groups / carrier groups #0 to #N in the system, at least some LBT-SB groups / carrier groups in which LBT idle should be confirmed can be configured / indicated / determined for the UE. For example, based on the LBT result that some LBT-SB groups / carrier groups are confirmed as idle, the UE can be allowed to start FFP-u transmission in the COT initiated by the UE, restrictively for specific LBT-SB groups / carrier groups or LBT-SB / carrier groups including specific LBT-SB / carrier groups. When the UE starts FFP-u transmission in this manner, the LBT-SB / carrier group can be defined as necessarily including the corresponding UL signal. For example, the LBT-SB / carrier group can be configured as cell common / UE group common, or predefined.

[0264] 6) In the example of FFP-g and FFP-u, the start time of FFP-g may be set earlier than the start time of FFP-u (in a state where the interval between the start times of FFP-g and FFP-u is set to be less than {0.5*FFP period}) in the corresponding period (for example, Fig.16 (a)).

[0265] A. For example, the start time of FFP-g may be set to be {25usec+a, 9usec+a, or 16usec+a} or an equivalent number of OFDM symbols earlier than the start time of FFP-u.

[0266] i. Conversely, the start time of FFP-u may be set to align with the start time of the idle period of FFP-g (e.g. Fig.16 (b)).

[0267] B. In addition, given the start / end time of the FFP-g idle period (as defined in the legacy Release 16), the start time of FFP-u may be configured to be aligned with the start time of the FFP-g idle period (in a state where the start time of FFP-u is configured not to be aligned with the start time of FFP-g) (e.g., Fig.16 (c)).

[0268] 7) The following method may be considered to configure / signal the FFP start time and FFP duration / period of the FFP-u of the UE. For reference, for FFP-g in the legacy Release 16 NR system, the FFP start time is set by starting offset = 0 based on an even radio frame number, and the FFP-g period (starting period) and the FFP duration (occupied period) are set to be equal.

[0269] A. The granularity of the start offset of FFP-u may be configured / predefined as one of {OFDM symbol unit, time slot unit, millisecond (and / or usec) unit} or a combination of two (or three) of the units). Information about the actual start offset based on the corresponding granularity may be explicitly / implicitly configured / indicated to the UE.

[0270] i. For example, assuming that symbol-level granularity is used for the starting offset of FFP-u (e.g., Fig.17 ), the actual starting offset value may be configured / indicated as X symbols. Various other granularities may be used for the starting offset. For example, the starting offset may be configured as Y slots, Z milliseconds (and / or usecs), {Y slots + X symbols}, or {Z milliseconds (and / or usecs) + X symbols}.

[0271] ii. According to a more specific embodiment, the starting offset value of FFP-u (especially in a symbol or slot) may vary depending on the SCS size. For example, when a set of symbol-level or slot-level starting offset values ​​configurable for an SCS of N KHz is given as {a, b, c}, a set of configurable offset values ​​for an SCS of (N x 2K) KHz may be given as {a x2K, bx 2K, cx 2K}. In a more specific example, assuming that a first value is indicated / configured to / for a UE as a starting offset, the first value may be interpreted as an L1 symbol for SCS1, and as an L2 symbol for an SCS2 different from SCS1. L1 and L2 may be different natural numbers. L1 and L2 may be set so that the total duration (length) corresponding to an L1 symbol based on SCS1 is equal to the total duration (length) corresponding to an L2 symbol based on SCS2. For example, although multiple UEs operate based on different SCSs, multiple UEs may have the same understanding of the starting time and period of FFP-u in the time domain. For example, with respect to the starting offset and period (e.g., COT, idle period, and / or CCA slot) of FFP-u, time alignment between UE1 operating based on SCS1 and UE2 operating based on SCS2 may be possible. For example, compared with UE-specific signaling, the BS / network may configure / indicate / signal information about the starting offset and period of FFP-u to / for multiple UEs (UE groups) in common, thereby reducing overhead. The SCS on which the starting offset and period of FFP-u indicated by the BS / network are based may be configured / predefined, and this SCS may be referred to as a reference SCS.

[0272] iii. When symbol-level granularity is used for FFP-u, efficiency and scheduling flexibility of the configured licensed UL (e.g., CG PUSCH) defined in the current NR system can be guaranteed. For the configured licensed UL operation, the start of the UL resources is preconfigured / pre-allocated at the symbol level. If FFP-u has a granularity at a larger level than the symbol level, for example, at the slot level, some configured UL resources may not be available for FFP-u due to misalignment between the configured UL resources and FFP-u. Therefore, resource efficiency, scheduling flexibility and / or low latency performance may be reduced. Therefore, it is preferred to configure / define the granularity of the start offset of FFP-u at the symbol level.

[0273] B. The upper limit of the start offset of FFP-u can be determined based on the period (duration) of FFP-u. When the period of FFP-u is set to W, the start offset of FFP-u can be set / selected from values ​​equal to or greater than 0 and less than W. For example, refer to Fig.17, the starting offset of FFP-u may be set below the period W of FFP-u. In a more specific example, when the period of FFP-u is set to W1 milliseconds (and / or usec), the starting offset of FFP-u may be set to one of M candidate offset values ​​within a range of 0 to less than W1 milliseconds (and / or usec).

[0274] i. In this case, M candidate offset values ​​may be equally defined for each of the different W1 values. As the value of W1 increases / decreases, the interval between adjacent candidate offset values ​​may be set to further increase / decrease.

[0275] ii. For example, when for W1 = A, the set of configurable candidate offset values ​​is given as {a, b, c}, the set of configurable candidate offset values ​​can be given as {ax K, bx K, cx K} = (A x K) for W1.

[0276] iii. In another method, when the period of FFP-g (or the maximum or minimum value between the period of FFP-g and the period of FFP-u) is set to W2 milliseconds (and / or usec) (regardless of the period set for FFP-u), the start offset of FFP-u may be set to one of L candidate offset values ​​in the range of 0 to less than W2 milliseconds (and / or usec). In this case, L candidate offset values ​​may also be defined equally for each of different W2 values, and as the value of W2 increases / decreases, the interval between adjacent candidate offset values ​​may be set to further increase / decrease, similar to the above example.

[0277] C. Where the period of FFP-g is set to W3 milliseconds (and / or usec), the period of FFP-u may be set to one of K candidate period values ​​corresponding to a factor of W3, including W3 milliseconds (and / or usec).

[0278] i. In this case, K candidate period values ​​may be equally defined for each of the different W3 values. As the value of W3 increases / decreases, the interval between adjacent candidate period values ​​may be set to further increase / decrease.

[0279] ii. For example, when for W3=B, the set of configurable candidate period values ​​is given as {a, b, c}, for W3=(B x K), the set of configurable candidate period values ​​can be given as {ax K, bx K, cx K}.

[0280] iii. According to the above description, the period of FFP-u can be set only as a factor of the period of FFP-g, rather than a value other than the factor.

[0281] D. The period for periodic (P) or semi-persistent (SP) UL signal / channel (e.g., CG PUSCH, P / SP-CSI, SR, P / SP-SRS, or PRACH) transmission can be set only to 1) a value equal to the period of FFP-u, 2) a factor of the period of FFP-u, or 3) a multiple of the FFP-u period.

[0282] i. According to the above description, (the period of the P / SP-UL signal / channel) may not be set to a value other than a factor or multiple of the FFP-u period.

[0283] E. For the period (e.g., starting period) and duration (e.g., occupation period) of FFP-u, the period P of FFP-u can be set to a value greater than the duration D of FFP-u (e.g., so that P is a multiple of D) (different from the existing FFP-g).

[0284] i. For example, for FFP-g, period = duration = C milliseconds (and / or usecs), as is conventionally done, whereas for FFP-u, duration = C milliseconds (and / or usecs) and period = C x K milliseconds (and / or usecs) (e.g., K>=1).

[0285] ii. From the BS's perspective, this setting can achieve more stable DL transmission because, although FFP-g and FFP-u overlap each other within a specific FFP period, only FFP-g exists (does not overlap with FFP-u) in the remaining FFP periods.

[0286] 8) The FFP-g period and FFP-u period configurable for the UE may be restricted / limited in the following method.

[0287] A. Table 8 below lists a total of 36 cycle combinations that can be generated from 6 FFP-g cycles and 6 FFP-u cycles.

[0288] i. In Table 8, the FFP-g period and the FFP-u period are equal or in a multiple / factor relationship in the 24 combinations marked with "O".

[0289] ii. In Table 8, in the 2 combinations labeled "P5", the least common multiple between the FFP-g period and the FFP-u period is 5 milliseconds (eg, the overlapping pattern between FFP-g and FFP-u repeats every 5 milliseconds).

[0290] iii. In Table 8, in the 4 combinations labeled "P10", the least common multiple between the FFP-g period and the FFP-u period is 10 milliseconds (eg, the overlapping pattern between FFP-g and FFP-u is repeated every 10 milliseconds).

[0291] iv. In Table 8, in the 6 combinations labeled "P20", the least common multiple between the FFP-g period and the FFP-u period is 20 milliseconds (eg, the overlapping pattern between FFP-g and FFP-u is repeated every 20 milliseconds).

[0292] v. In Table 8, in the 6 combinations labeled "5:2", the overlapping pattern period includes 5 FFP-g's and 2 FFP-u's or 2 FFP-g's and 5 FFP-u's.

[0293] vi. In Table 8, in the 4 combinations labeled "5:4", the overlapping pattern period includes 5 FFP-g's and 4 FFP-u's or 4 FFP-g's and 5 FFP-u's.

[0294] vii. In Table 8, in the 2 combinations labeled "5:8", the overlapping pattern period includes 5 FFP-g's and 8 FFP-u's or 8 FFP-g's and 5 FFP-u's.

[0295] viii. As the least common multiple of the FFP-g period and the FFP-u period, that is, the overlapping pattern period of FFP-g and FFP-u decreases, the LBT sensing time of the UE / BS and the repetitive pattern period of the idle period decrease, thereby relatively reducing the operation complexity of the UE / BS.

[0296] ix. As the number of FFP-u and / or FFP-g included in the overlapping pattern period between FFP-g's and FFP-u's decreases, the LBT sensing time of the UE / BS and the repetitive pattern period of the idle period decrease, thereby relatively reducing the operation complexity of the UE / BS.

[0297] x. In addition, considering the characteristics of UL data services of URLLC UEs that require low latency, it may be necessary to set the FFP-u period to a small value.

[0298] [Table 8]

[0299]

[0300] B. Based on Table 8 above, the FFP-g / FFP-u periodic combinations configurable for the UE may mainly include 24 combinations corresponding to "0", and further include the next X combinations among the remaining 12 combinations (for example, it may be specified that the remaining combinations except for 24+K combinations should not be configured for the UE).

[0301] i. Method 1: Corresponding to the combination of "P5" (X = 2)

[0302] ii. Method 2: Combinations corresponding to "P5" or "P10" (X = 6)

[0303] iii. Method 3: Combinations corresponding to "5:2" (X = 6)

[0304] iv. Method 4: Combinations corresponding to "5:2" or "5:4" (X = 10)

[0305] v. Method 5-1: Combinations with an FFP-u period of 1 millisecond (X = 1)

[0306] vi. Method 5-2: Combinations with an FFP-u period of 1 millisecond and an FFP-g period of 1 millisecond (X = 2)

[0307] vii. Method 6-1: Combinations with an FFP-u period of 1 millisecond or 2 milliseconds (X = 3)

[0308] viii. Method 6-2: Combinations with an FFP-u period of 1 millisecond or 2 milliseconds and an FFP-g period of 1 millisecond or 2 milliseconds (X = 6)

[0309] ix. Method 7-1: Combinations with an FFP-u period of 1 millisecond, 2 milliseconds, or 2.5 milliseconds (X = 6)

[0310] x. Method 7-2: Combinations with an FFP-u period of 1 millisecond, 2 milliseconds, or 2.5 milliseconds and an FFP-g period of 1 millisecond, 2 milliseconds, or 2.5 milliseconds (X = 8)

[0311] xi. Method 8: Combinations with an FFP-u period < FFP-g period relationship (X = 6)

[0312] [Proposal 2]

[0313] 1) Whether UE-initiated COT generation operations are allowed for the FFP configured before FFP-n (i.e., FFP_n-k) can be indicated to the UE through specific signaling sent in the FFP. That is, for the FFP configured at a specific time (i.e., FFP_n).

[0314] A. When it is indicated that UE-initiated COT generation operations are allowed, the UE can perform LBT shortly before the start time of FFP_N (e.g., 25 - usec, 9 - usec, or 16 - usec).

[0315] i. When it is determined that the channel is idle as a result of LBT, the UE can start sending FFP_n in the UE-initiated COT.

[0316] ii. Otherwise, when the channel is determined to be busy, UE operation may be defined where the UE performs Release 16 operation assuming that the FFP-n transmission structure starts with a BS-initiated COT, or the UE does not perform transmission (and / or reception) in the FFP-n period.

[0317] B. When it is indicated that UE-initiated COT is not allowed, the UE may perform Release 16 operation assuming that the FFP-n transmission structure starts with BS-initiated COT.

[0318] C. In addition, information on the maximum duration allowed for UE-initiated COT may be configured by RRC signaling or indicated by DCI (and / or MAC) signaling.

[0319] 2) To enable efficient COT transmission between multiple UEs (and / or between UE and BS) in TDM with minimized collisions between COT transmissions, the following operations may be considered in a method of configuring / indicating a maximum duration for transmission based on UE-initiated COT.

[0320] A. The maximum duration of UE-initiated COT-based transmission allowed in one FFP-u period (referred to as "maximum COT duration" for convenience) may be configured / indicated to the UE by RRC (or DCI or MAC) signaling.

[0321] i. For the maximum COT duration, one value may be commonly configured / indicated for all FFP-u periods, for each FFP-u period, or for each FFP-u period set (i.e., each set of FFP-u periods). For example, assuming there are a total of N FFP-u periods, FFP-u period #0 to FFP-u period #N-1. For example, the same maximum COT duration may be commonly configured for FFP-u period #0 to FFP-u period #N-1. Alternatively, the maximum COT duration may be independently configured for each individual FFP-u period. Alternatively, a maximum COT duration configuration / indication method based on a FFP-u period group / set may be used, such as configuration / indication of a first maximum COT duration for a first group of FFP-u periods and a second maximum COT duration for a second group of FFP-u periods among a total of N FFP-u periods.

[0322] B. As the UE operation in the remaining period except the maximum COT duration in the front part of the FFP-u period (for convenience, referred to as "behavior after COT"), one of the following Alt 1 and Alt 2 (and / or Alt 3) may be configured / indicated to the UE through RRC (or DCI or MAC) signaling, or one of the following Alt 1 and Alt 2 (and / or Alt 3) (e.g., Alt 2 (and / or Alt 3)) may be defined (without any separate configuration / indication).

[0323] i. Alt 1: Only UL (eg, PUSCH or PUCCH) transmission based on shared COT (based on BS-initiated COT) is possible.

[0324] ii.Alt 2: UL transmission is not allowed.

[0325] iii. Alt 3: Only DCI-scheduled UL (eg, PUSCH or PUCCH) transmissions are possible.

[0326] iv. Furthermore, in case of post-COT behavior, one value may be configured / indicated commonly for all FFP-u periods, for each FFP-u period, or for each FFP-u period set (ie, each set of FFP-u periods).

[0327] C. In addition, when the FFP-u period includes the start time of the FFP-g period, (the maximum COT duration may be configured / indicated as described above, or) without any separate configuration / indication, the time period between the start time of the FFP-u and the start time of the FFP-g period may be defined as the maximum COT duration.

[0328] i. In this case, the behavior after COT can be defined as Alt 1 (without any separate configuration / instruction).

[0329] D. Alternatively, when the FFP-u period includes the start time of the FFP-g period, it may be configured / indicated for / to the UE whether Alt A) the time period between the start time of the FFP-u period and the start time of the FFP-g period is applied as the maximum COT duration or Alt B) this separate limit is not imposed on the COT duration transmitted by the UE via RRC (or DCI or MAC) signaling.

[0330] i. For example, Alt A may be performed as a default operation (until a separate configuration / instruction is performed), and it may be configured / indicated whether Alt B is performed. Alternatively, Alt B may be performed as a default operation (until a separate configuration / instruction is performed), and it may be configured / indicated whether Alt A is performed.

[0331] ii. Also in this case, the behavior after COT can be defined as Alt 1 (without any separate configuration / instruction).

[0332] E. In addition, when the FFP-u period does not include the start time of the FFP-g period, the behavior after COT (after the configured / indicated maximum COT duration) can be defined as Alt 2 (and / or Alt 3) (without any separate configuration / indication).

[0333] 3) Specific signaling indicating whether UE-initiated COT is allowed may be configured / sent as UE (group) common DCI or UE-specific (UL grant) DCI.

[0334] A. The DCI may explicitly indicate whether FFP-n starts with a UE-initiated COT. When the DCI is a UE (group)-common DCI, the DCI may indicate for each UE (group) individually or independently whether it is allowed to generate a UE-initiated COT at the start time of FFP-n (and / or information indicating the number of FFP periods in which UE-initiated COT is allowed).

[0335] i. Alternatively, it may be implicitly indicated whether the configured UL resources configured at a specific time in the FFP-n cycle (e.g., a symbol / slot in the front part) are cancelled (in this case, UE-initiated COT is not allowed) (in this case, UE-initiated COT is allowed).

[0336] B. And / or, the COT / FFP type scheduled / allowed in a subsequent (e.g., immediately following) FFP period (e.g., whether FFP-g transmissions starting with a BS-initiated COT or transmissions starting with a UE-initiated COT are scheduled) can be indicated by a DCI (e.g., DCI format 2_0) sent in a particular (current) FFP period that indicates the COT duration and a slot format information (SFI) structure.

[0337] i. For example, the UE (group) combines the COT duration and SFI structure information corresponding to the UE (group) among the fields of the DCI sent with the signal, and the SFI information includes the DL / UL configuration of the time period after (the end time) of the current FFP period as a result of the combination, when the SFI information indicated for the corresponding time period (a specific time point in the time period (e.g., the first symbol)) is DL (symbol), FFP-g transmission starting with BS-initiated COT can be scheduled in the next FFP period (or FFP-u transmission starting with UE-initiated COT is not allowed), and when the SFI information indicated for the corresponding time period is UL (symbol), FFP-u transmission starting with UE-initiated COT can be allowed in the next FFP period of the UE (group).

[0338] ii. In addition, the SFI information of the DCI indicated for this time period is flexible (symbol), 1) FFP-g transmission starting with BS-initiated COT or FFP-u transmission starting with UE-initiated COT may not be scheduled / allowed in the next FFP period, or 2) only scheduled PUSCH / PUCCH transmissions (indicated by DCI) may be allowed in the next FFP period, while configured PUSCH / PUCCH transmissions (configured in the FFP period) may not be allowed in the next FFP period.

[0339] iii. In another method, when the SFI information of the DCI indicated for the time period is DL and / or flexible (symbol), FFP-u transmission starting with UE-initiated COT may not be allowed in the next FFP period, however, when the SFI information of the DCI indicated for the time period is UL (symbol), FFP-u transmission starting with UE-initiated COT may be allowed in the next FFP period.

[0340] iv. In another method, when the SFI information of the DCI indicated for the time period is DL (symbol), FFP-u transmission starting with UE-initiated COT may not be allowed in the next FFP period, however, when the SFI information of the DCI indicated for the time period is UL and / or flexible (symbol), FFP-u transmission starting with UE-initiated COT may be allowed in the next FFP period.

[0341] C. Alternatively, it may indicate whether non-UL (e.g., DL) or UL resources configured at a specific time in an FFP-n cycle (e.g., a symbol / slot in the front part) are covered / confirmed as UL (in this case, UE-initiated COT is allowed) or not (in this case, UE-initiated COT is not allowed).

[0342] i. In this case, the DCI may indicate the SFI. Here, the DCI may indicate the SFI of the FFP configured after the transmitted FFP, and / or a single DCI may indicate the SFI of multiple FFPs at the same time.

[0343] D. Alternatively, it may be indicated whether UL resources are allocated for scheduling PUSCH transmission at a specific time in the FFP-n cycle (e.g., symbols / slots in the front part) (in this case, UE-initiated COT is allowed) (in this case, UE-initiated COT is not allowed).

[0344] 4) In another method, the BS may indicate to the UE whether to use / send a specific (e.g., immediately following) FFP-g period (transmission based on the shared COT in the period) in the period of the COT generated by the BS (FFP-g period starting with the COT) (generated by the COT) through specific signaling. The UE may receive specific signaling (transmission based on the shared COT in the period) in the period of the COT generated by the BS (FFP-g period starting with the COT) and determine whether to send / use (specific (e.g., immediately following) FFP-g period) based on the specific signaling (generated by the COT).

[0345] A. In another method, the UE can indicate to the BS (and other UEs) through specific signaling whether to send / use a specific (e.g., immediately following) FFP-g period (shared COT-based transmission in the period) in the period of the COT generated with it (FFP-u period starting with the COT) (generated by the COT).

[0346] [Proposal 3]

[0347] 1) When a specific FFP starts with transmission based on UE-initiated COT, all configured UL (e.g., PRACH or PUSCH) resources configured in the FFP period may be determined as valid UL resources (UL resources that may be transmitted by the UE) (regardless of whether there is a conflict with DL).

[0348] A. In addition, (configured) DL resources may be covered by UL in the FFP period starting with UE-initiated COT. (Unlike this, UL resources may be covered by DL (and DL resources may not be covered by UL), as is conventionally done, in the FFP period starting with BS-initiated COT.)

[0349] 2) The UL / DL configuration applied to the FFP period starting with the UE-initiated COT (ie, FFP-u period) and the UL / DL configuration applied to the FFP period starting with the BS-initiated COT (ie, FFP-g period) may be independently (eg, differently) configured.

[0350] [Proposal 4]

[0351] 1) According to an example of the present disclosure, a CP configuration / parameter for a UL signal may be determined depending on whether the start of FFP-u is aligned with the start (symbol) of the UL signal. A first CP extension parameter value (e.g., extended CP length) may be configured / applied for CP extension applied to a UL signal (e.g., PUSCH / PUCCH / PRACH) resource transmission configured or scheduled to have a start symbol aligned with the start time of FFP-u starting with a UE-initiated COT (and / or after a specific time or less from the start time), and a second CP extension parameter may be configured / determined for a UL signal (e.g., PUSCH / PUCCH / PRACH) resource transmission configured or scheduled not to be aligned with the start time of FFP-u. The UE / BS may independently (e.g., differently) determine / apply the first CP extension parameter value and the second CP extension parameter value.

[0352] A. For example, for a UL signal transmitted based on a configured grant or RRC configuration, for example, a configured PUSCH (and / or PRACH and / or PUCCH), the following method may be considered.

[0353] –Opt 1: In the case where a CP extension parameter value is configured to be commonly applied to all configured PUSCH resources (or all configured PRACH / PUCCH resources), CP extension can be exceptionally performed for PUSCH (PRACH / PUCCH) resources configured to be aligned with the start time of FFP-u, so that the start time of the corresponding signal is accurately aligned with the start time of FFP-u.

[0354] –Opt 2: Separate / independent CP extension parameter values ​​(e.g., extended CP length) may be configured for configured PUSCH (PRACH / PUCCH) resources that are configured not to be aligned with the start time of FFP-u and configured PUSCH (PRACH / PUCCH) resources that are configured to be aligned with the start time of FFP-u. To further summarize, a CP extension parameter value (e.g., extended CP length) may be configured separately / independently for each configured PUSCH (PRACH / PUCCH) resource.

[0355] B. In another example, the following method may be considered for a UL signal transmitted based on a dynamic UL / DL grant DCI, such as a scheduled PUSCH (and / or PUCCH).

[0356] –Opt 1: In the case where multiple candidate CP extension parameter values ​​(i.e., candidate CPE value sets) have been commonly configured for all scheduled PUSCH resources (or all scheduled PUCCH resources) (and one of the candidate CP extension parameter values ​​is indicated by DCI), for PUSCH (PUCCH) resources indicated as aligned with the start time of FFP-u, CP extension can be exceptionally performed (by determining / applying the extended CP length) so that the start time of the signal is accurately aligned with the start time of FFP-u.

[0357] – Opt 2: Separate / independent candidate CPE value sets (e.g., extended CP length) may be configured for PUSCH (PRACH / PUCCH) resources that are configured to be scheduled aligned with the start time of FFP-u and PUSCH (PRACH / PUCCH) resources that are configured to be scheduled not aligned with the start time of FFP-u.

[0358] [Proposal 5]

[0359] 1) When a specific signal transmitted from a UE is successfully detected in an FFP-u period (starting with a UE-initiated COT), the BS may also perform shared COT-based DL transmission in the same FFP-u period, and such shared COT-based transmission from the BS may only be allowed until (shortly before) the start time (maximum) of the idle period configured in the FFP-u period.

[0360] A. In this case, when the BS detects UL signals transmitted from multiple UEs in the FFP-u period and the start times of (multiple) idle periods configured for the UEs are set to different times, the BS may be allowed to perform transmission based on the shared COT 1) until (shortly before) the earliest or last of the start times of the idle periods, or 2) until (shortly before) the start time of the idle period configured for the UE scheduled by the BS to send DL / UL grant DCI in the FFP-u period.

[0361] 2) For the FFP-u period starting with a COT initiated by the UE, the portion occupied by the idle period in the FFP-u period or the start / end time of the idle period in the FFP-u period may be configured through RRC signaling or indicated through DCI / MAC signaling (there is no fixed value, such as the existing FFP-g starting with a COT initiated by the BS).

[0362] A. And / or, in a case where the network has independently (e.g., differently) configured the FFP-u start time for each of the multiple UEs, the start time of the idle period in the FFP-u period may be set to be the same for all the multiple UEs.

[0363] [Proposal 6]

[0364] 1) Various FFP types may be defined / configured according to the type of DL / UL transmission signal / channel configured to have alignment with the FFP start time (and / or after a specific time or less from the start time) (and / or configured in the FFP period (without overlapping with the idle period). The various types may include all or at least one of the three FFP types, a) a default FFP-g that starts only with a BS-initiated COT, b) a default FFP-u that starts only with a UE-initiated COT, and / or c) a flexible FFP that may start from one of a BS-initiated COT and a UE-initiated COT.

[0365] A. When a specific DL signal / channel (e.g., broadcast SSB (e.g., resources used for SS / PBCH transmission) and / or a specific transmission (configured by MIB / SIB) (e.g., CORESET (e.g., with the lowest ID / index)) transmission is configured at the start time of a specific FFP or within the FFP period, the FFP may be defined / configured as the default FFP-g.

[0366] i. Therefore, for an FFP corresponding to the default FFP-g (and / or overlapping with the default FFP-g), FFP-u configuration / transmission generated by a UE-initiated COT may not be allowed (thus, the UE may not have performed an LBT operation shortly before the start time of the FFP for COT initiation), and the UE may only be allowed to perform shared COT-based transmission within the FFP period (thus, the UE may first detect a DL signal sent from the BS in the FFP period).

[0367] B. When a specific UL signal / channel (e.g., PRACH) transmission is configured at the start time of a specific FFP, the FFP may be defined / configured as a default FFP-u. For example, when the start time of a specific FFP overlaps with a PRACH opportunity, the FFP may be defined / configured as a default FFP-u.

[0368] i. Therefore, for an FFP corresponding to a default FFP-u (and / or overlapping with the default FFP-u), FFP-g configuration / transmission generated by a BS-initiated COT may not be allowed (thus, the BS may not have performed an LBT operation shortly before the FFP start time for COT initiation), and only shared COT-based transmission in the FFP period may be allowed for the BS (thus, the BS may first detect a UL signal sent from the UE in the FFP period).

[0369] C. Other FFPs that are not defined / configured as default FFP-g or default FFP-u may be defined / configured as flexible FFPs.

[0370] i. Based on LBT results of BS and UE and / or specific signaling and / or DL / UL grant DCI scheduling / indication, these flexible FFPs can be flexibly configured / sent as FFP-g's or FFP-u's (over time).

[0371] 2) In the case where multiple LBT-SBs (eg, RB sets (+ protection RBs)) and / or multiple carriers have been configured for the UE, the following operations may be considered.

[0372] A. When (for a specific FFP period), at least one LBT-SB or at least one carrier is configured as a default FFP-g in an LBT-SB group including multiple LBT-SBs in one carrier (and / or multiple in-band carriers), a carrier group including multiple in-band carriers, or an LBT-SB group / carrier group whose availability is indicated by the same bit of PDCCH, when the availability is indicated for the LBT-SB / carrier by specific signaling (e.g., GC-PDCCH), assuming that the FFP-g transmission structure starts with a BS-initiated COT for all LBT-SBs / carriers in the LBT-SB group / carrier group to which the corresponding LBT-SB / carrier belongs (for the corresponding FFP period), the UE can perform Release 16 operation.

[0373] This example can be extended to the case where a specific LBT-SB group includes a single LBT-SB and / or a specific carrier group (CG) includes a single carrier, and is not necessarily limited to multiple LBT-SBs / multiple carriers. For example, when default FFP-g's are configured in at least a portion of a specific LBT-SB group (regardless of the number of LBT-SBs included in the specific LBT-SB group), assuming that the FFP-g transmission structure starts with a BS-initiated COT for the entire specific LBT-SB group (for the corresponding FFP period), the UE can perform Release 16 operation. For example, when default FFP-g's are configured in at least a portion of a specific CG (regardless of the number of carriers included in the specific CG), assuming that the FFP-g transmission structure starts with a BS-initiated COT for the entire specific CG (for the corresponding FFP period), the UE can perform Release 16 operation.

[0374] i. Therefore, the UL resources (e.g., (CG)PUSCH, PRACH, or PUCCH) configured at the start time of FFP-u in the LBT-SB / carrier in the LBT-SB / carrier group (to which the LBT-SB / carrier constructed / configured with the default FFP-g belongs) (including in the default FFP-g's period and / or overlapping with the transmission time of a specific DL signal / channel) may be canceled or treated as invalid, and / or for the UL resources (e.g., PUSCH or PUCCH) configured or scheduled at the start time of FFP-u, only the shared COT-based transmission based on the BS-initiated COT may be enabled / allowed, and / or for the UL resources configured / scheduled at the start time of FFP-u, only one-time transmission may be enabled / allowed (the BS is not allowed to perform shared COT-based DL transmission based on the corresponding transmission).

[0375] ii. Therefore, for the FFP assumed to be FFP-g (the entire LBT-SB group / carrier group in the corresponding period), the generated FFP-u configuration / transmission by the UE-initiated COT is not allowed (or only the transmission based on the shared COT can be allowed in the corresponding FFP period for the UE). This may be intended to prevent the impact of (UL to DL) interference caused by the transmission based on the UE-initiated COT on the BS-initiated COT / FFP. For example, the conflict / interference between the BS-initiated COT and the UE-initiated COT can be prevented.

[0376] B. Otherwise, when all LBT-SBs or all carriers in an LBT-SB group or a carrier group are not configured with default FFP-g's, the UE may start corresponding FFP-u transmission in a UE-initiated COT in the LBT-SBs / carriers in the LBT-SB group / carrier group (all LBT-SBs / carriers or some LBT-SBs / carriers (LBT result is idle)).

[0377] C. The LBT-SB group / carrier group may be determined as all multiple LBT-SBs configured / constructed in one carrier (and / or multiple in-band carriers) or multiple in-band carriers, or may be determined / limited to the LBT-SB / carrier in which the UE will perform actual UL channel / signal transmission or the LBT-SB / carrier configured / indicated for UL channel / signal transmission from the UE (within the corresponding FFP period). For example, when there are LBT-SB groups / carrier groups #0 to #N in the system, and the UE intends to perform UL channel / signal transmission or is configured / indicated to perform UL channel / signal transmission in some LBT-SB groups / carrier groups #0 to #N (hereinafter referred to as specific LBT-SB groups / carrier groups), the UE may be allowed to start the corresponding FFP-u transmission in the UE-initiated COT based on the absence of a default FFP-g construction / configuration in the entire specific LBT-SB group / carrier group.

[0378] D. In further generalization, in order to start FFP-u transmission in a UE-initiated COT in the presence of LBT-SB groups / carrier groups #0 to #N in the system, at least some LBT-SB groups / carrier groups may be configured / indicated / determined for / to the UE only when it is confirmed that there is no default FFP-g configuration / configuration. For example, based on the fact that no default FFP-g configuration / configuration is identified in some LBT-SB groups / carrier groups, the UE may be allowed to start FFP-u transmission in the UE-initiated COT, restrictively for some LBT-SB groups / carrier groups or for LBT-SB / carrier groups including the corresponding LBT-SB / carrier groups. When the UE starts FFP-u transmission in this manner, the LBT-SB / carrier group may be defined to necessarily include the corresponding UL signal. For example, the LBT-SB / carrier group may be configured or predefined cell-wide / UE-group-wide.

[0379] Fig.18 is a diagram illustrating a method for performing CAP on a shared spectrum by a UE in a wireless communication system according to an embodiment of the present disclosure. Fig.18 The embodiments are exemplary application methods proposed above and do not limit the scope of the present disclosure. Fig.18 For embodiments of the present invention, reference may be made to the foregoing description.

[0380] refer to Fig.18 , the UE obtains FFP related information for FBE (H05). The FFP related information may include information about the FFP start offset and information about the FFP duration / period.

[0381] For example, FFP related information can be obtained through higher layer signaling. The BS can send FFP related information for FBE. The UE can identify the start time of the corresponding FFP based on the FFP start offset with OFDM symbol level granularity. The maximum value of the FFP start offset with OFDM symbol level granularity can be determined based on the length of the FFP duration / cycle. The first time length indicated by the information about the FFP start offset can be set to be less than the second time length indicated by the information about the FFP duration / cycle. The BS can indicate the first time length determined based on the OFDM symbol level granularity through information about the FFP start offset.

[0382] The UE may perform a clear channel assessment (CCA) on at least one FFP starting with a UE-initiated channel occupation time (COT) based on the FFP-related information (H10).

[0383] The UE transmits a UL signal in the FFP determined based on the CCA (H15). When transmission cannot be started, the UE may transmit a UL signal based on the COT initiated by the shared BS.

[0384] The BS may monitor the UL signal in each FFP starting with the UE-initiated COT based on the FFP-related information.

[0385] When the UE cannot initiate its COT in the corresponding FFP as a result of CCA due to busy channels, the UE may transmit a UL signal based on the COT initiated by the shared BS.

[0386] At least one FFP started with a COT initiated by the UE may be a first type FFP, and the FFP started with a COT initiated by the BS may be a second type FFP different from the first type FFP. The start of the first type FFP may not be time-aligned with the start of the second type FFP. The start of the idle period included in the first type FFP may be time-aligned with the start of the idle period included in the second type FFP.

[0387] Fig.19 A communication system 1 applied to the present disclosure is shown.

[0388] refer to Fig.19, the 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 a head mounted device (HMD), a head up display (HUD) installed in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. Handheld devices may include smart phones, smart boards, 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.

[0389] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without passing through the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0390] Wireless communication / connection 150a, 150b or 150c may be established between wireless devices 100a to 100f / BS 200 or BS 200 / BS 200. Herein, wireless communication / connection may be established through 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 send / receive radio signals to / from each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b may send / receive signals through various physical channels. To this end, at least a portion of various configuration information for configuring a process for sending / receiving a radio signal, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and a resource allocation process may be performed based on various proposals of the present disclosure.

[0391] Fig. 20 A wireless device suitable for use with the present disclosure is shown.

[0392] refer to Fig. 20 , the first wireless device 100 and the second wireless device 200 may 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 Fig.19 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

[0393] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and 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 description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 102 may process the information in 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 codes including commands for executing part or all of the processes controlled by the processor 102 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. 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 through 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 the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0394] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and 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 description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 202 may process the information in 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 codes including commands for executing part or all of the processes controlled by the processor 202 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. 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 through 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 the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0395] In the following, 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. 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 description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document, and provide the generated signal to one or more transceivers 106 and 206. 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 description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.

[0396] 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 flow charts 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 flow charts 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.

[0397] 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 disk drive, register, cache memory, computer-readable storage medium and / or a combination thereof. One or more memories 104 and 204 may be located inside and / or outside of 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 by various technologies such as wired or wireless connections.

[0398] One or more transceivers 106 and 206 may send user data, control information and / or radio signals / channels mentioned in the method and / or operation flow chart 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 description, function, process, proposal, method and / or operation flow chart 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 send and receive radio signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information or radio signals to one or more other devices. One or more processors 102 and 202 may perform 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 send and receive user data, control information and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods and / or operation 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 as to process received user data, control information, radio signals / channels, etc. 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.

[0399] Fig.21 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be used according to the usage / service (reference Fig.19 ) are implemented in various forms.

[0400] refer to Fig.21 , the wireless devices 100 and 200 may correspond to Fig. 20The wireless devices 100 and 200 of the present invention may be configured by various elements, components, units / parts 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 Fig. 20 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig. 20 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 send information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

[0401] 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: Fig.19 100a), vehicles ( Fig.19 100b-1 and 100b-2), XR devices ( Fig.19 100c), handheld devices ( Fig.19 100d), household appliances ( Fig.19 100e), IoT devices ( Fig.19 100f), digital broadcasting terminals, holographic equipment, public safety equipment, MTC equipment, medical equipment, fintech equipment (or financial equipment), security equipment, climate / environmental equipment, AI servers / equipment ( Fig.19 400), BS( Fig.19 200), network nodes, etc. The wireless device can be used in a mobile or fixed location depending on the usage example / service.

[0402] exist Fig.21In the wireless devices 100 and 200, various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may all be connected to each other through a wired interface, or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. The various elements, components, units / parts and / or modules within the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a collection of one or more processors. As an example, the 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, the memory 130 may be configured by a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM)), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

[0403] Fig. 22 A vehicle or an autonomous vehicle applied to the present disclosure is shown. The vehicle or the autonomous vehicle can be implemented by a mobile robot, a car, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.

[0404] refer to Fig. 22 , 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 Fig.21 Block 110 / 130 / 140.

[0405] The communication unit 110 may send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or autonomous driving vehicle 100. The control unit 120 may include an electronic control unit (ECU). The drive unit 140a may enable the vehicle or autonomous driving vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a power system, wheels, brakes, a steering device, etc. The power supply unit 140b may supply power to the vehicle or autonomous driving vehicle 100, and include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c may acquire vehicle status, surrounding environment information, user information, etc. The sensor unit 140c 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 position 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 140d may implement a technology for maintaining a lane in which the vehicle is traveling, a technology for automatically adjusting a 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, and the like.

[0406] For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving path and a driving plan from the acquired data. The control unit 120 may control the drive unit 140a so that the vehicle or the autonomous driving vehicle 100 may move along the autonomous driving path according to the driving plan (e.g., speed / direction control). In the middle of autonomous driving, the communication unit 110 may aperiodically / periodically obtain the latest traffic information data from the external server and obtain surrounding traffic information data from neighboring vehicles.

[0407] In the middle of 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 about the vehicle position, autonomous driving path and / or driving plan to an external server. The external server may predict traffic information data using AI technology, etc. based on information collected from the vehicle or autonomous driving vehicle, and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0408] Fig.23 is a diagram illustrating a DRX operation of a UE according to an embodiment of the present disclosure.

[0409] The UE may perform DRX operation in the process and / or method described / proposed above. A UE configured with DRX may reduce power consumption by discontinuously receiving DL 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.

[0410] refer to Fig.23 , 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, the UE starts the inactivity timer and remains awake. On the contrary, when the UE fails to detect any PDCCH during the PDCCH monitoring, 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 process and / or method 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. On the contrary, 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.

[0411] 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 perform PDCCH monitoring discontinuously while executing the above-described / proposed procedures and / or methods.

[0412] [Table 9]

[0413]

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

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

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

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

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

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

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

[0421] When any one 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.

[0422] The above-mentioned embodiments correspond to the combination of elements and features of the present disclosure in a prescribed form. And, 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. And, it is obviously understandable that the embodiment is configured by combining claims that do not have an explicit reference relationship in the attached claims, or can be included as a new claim obtained by modification after submitting an application.

[0423] Those skilled in the art will appreciate that the present disclosure can be performed in other specific ways different from the ways set forth herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above embodiments are interpreted in all respects as illustrative and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents, rather than by the above description, and all changes falling within the meaning and equivalent range of the appended claims should be included therein.

[0424] Industrial Applicability

[0425] The present disclosure is applicable to UE, BS or other devices in a wireless mobile communication system.

Claims

1. A method for performing a channel access procedure on a shared spectrum in a wireless communication system by a user equipment (UE), the method comprising: Obtaining configuration information about channel access from a base station (BS); receiving, during a first period of time associated with a BS-initiated channel occupancy time (COT), downlink control information (DCI) for a scheduled uplink (UL) transmission associated with a UE-initiated channel occupancy; and performing a channel access procedure for scheduled UL transmission based on the configuration information, Wherein, in the case where the scheduled UL transmission is limited to a first time period associated with a BS-initiated COT, and the start of a second time period associated with a UE-initiated COT is not time-aligned: Based on the UE having initiated the channel occupation in the second time period, the UE performs the scheduled UL transmission, and Based on the UE not initiating the channel occupation in the second time period, the UE discards the scheduled UL transmission.

2. The method according to claim 1, wherein: The scheduled UL transmission occurs after the start of the second time period.

3. The method according to claim 1, wherein: The scheduled UL transmission is included in the second time period.

4. The method according to claim 1, wherein: The configuration information is obtained through higher layer signaling.

5. The method according to claim 1, wherein: The start of the first time period is not time aligned with the start of the second time period.

6. A non-computer readable medium storing a program for executing the method of claim 1.

7. A user equipment (UE) for performing a channel access procedure on a shared spectrum in a wireless communication system, the UE comprising: Transceiver; as well as a processor configured to: obtain configuration information about channel access from a base station (BS) by controlling the transceiver; receiving downlink control information (DCI) for a scheduled uplink (UL) transmission associated with a UE-initiated channel occupancy in a first period associated with a BS-initiated channel occupancy time (COT), and performing a channel access procedure for the scheduled UL transmission based on the configuration information, Wherein, in the case where the scheduled UL transmission is limited to a first time period associated with a BS-initiated COT, and the start of a second time period associated with a UE-initiated COT is not time-aligned: Based on the UE having initiated the channel occupation in the second time period, the UE performs the scheduled UL transmission, and Based on the UE not initiating the channel occupation in the second time period, the UE discards the scheduled UL transmission.

8. A method for performing a channel access procedure on a shared spectrum in a wireless communication system by a base station (BS), the method comprising: Sending configuration information about channel access to a user equipment (UE); as well as transmitting downlink control information (DCI) for scheduled uplink (UL) reception associated with UE-initiated channel occupancy in a first period associated with a BS-initiated channel occupancy time (COT), Wherein, in the case where the scheduled UL reception is limited to a first time period associated with the COT initiated by the BS, and the start of a second time period associated with the COT initiated by the UE is not time-aligned: Based on the UE having initiated the channel occupation in the second time period, the BS performs the scheduled UL reception, and Based on the UE not initiating the channel occupancy in the second time period, the BS abandons the scheduled UL reception.

9. The method according to claim 8, wherein: The scheduled UL transmission occurs after the start of the second time period.

10. A base station (BS) for performing a channel access procedure on a shared spectrum in a wireless communication system, the BS comprising: Transceiver; as well as a processor configured to: send configuration information about channel access to a user equipment (UE), and send downlink control information (DCI) for scheduled uplink (UL) reception associated with UE-initiated channel occupancy in a first period related to a BS-initiated channel occupancy time (COT), Wherein, in the case where the scheduled UL reception is limited to a first time period associated with the COT initiated by the BS, and the start of a second time period associated with the COT initiated by the UE is not time-aligned: Based on the UE having initiated the channel occupation in the second time period, the BS performs the scheduled UL reception, and Based on the UE not initiating the channel occupancy in the second time period, the BS abandons the scheduled UL reception.

Images